26 replies

Reconsidering `Either` Naming Convention to Reflect Its Role as a "Result" Type

Since swapping ye olde type parameter ordering (

<R, E, A>

<R, E, A>

) in favor of le nouveau one (

<A, E, R>

<A, E, R>

Either

Either

feels like it's in a pretty weird spot. Has any consideration been given to renaming/re-conceiving it to more formally acknowledge its conventional use as a "result" type, which encodes either success ("right") or failure ("left")? Even if that means reversing which direction is considered which. Elm did this with its

Result

Result

type (https://package.elm-lang.org/packages/elm/core/latest/Result), with variants

Ok

Ok

and

Err

Err

, and I've never heard any complaints. This kind of change feels like it would be very aligned with the latest change to the names of the two sides of a

Schema

Schema

(from

From

From

and

To

To

Type

Type

and

Encoded

Encoded

), which I think was a great move.

Effect Community•2y ago•

26 replies

Reconsidering `Either` Naming Convention to Reflect Its Role as a "Result" Type

Since swapping ye olde type parameter ordering (

<R, E, A>

<R, E, A>

) in favor of le nouveau one (

<A, E, R>

<A, E, R>

Either

Either

Result

Result

type (https://package.elm-lang.org/packages/elm/core/latest/Result), with variants

Ok

Ok

and

Err

Err

, and I've never heard any complaints. This kind of change feels like it would be very aligned with the latest change to the names of the two sides of a

Schema

Schema

(from

From

From

and

To

To

Type

Type

and

Encoded

Encoded

), which I think was a great move.

Reconsidering `Either` Naming Convention to Reflect Its Role as a "Result" Type

Similar Threads

Reconsidering `Either` Naming Convention to Reflect Its Role as a "Result" Type

Similar Threads

Similar Threads

Similar Threads