You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Validation Case Study, the Transforming data section begins with a description of how there are not enough types to actually perform a transformation. This makes sense but Either is used in the examples here. Just before this section was a the addition of the or combinator, and before that was converting from using Either to using Validated.
Example from the Transforming data section:
To implement map we need to change the definition of Check.
Specifically, we need to a new type variable
to separate the input type from the output:
typeCheck[E, A, B] =A=>Either[E, B]
Then later in the Predicates section Validated is again used.
I propose that Validated be used throughout this document, rather than Either.
The text was updated successfully, but these errors were encountered:
Thanks for looking at this @mmynsted. I think in the medium term we need to rewrite this and parts of the monads/applicatives chapters to use Parallel.
In the Validation Case Study, the Transforming data section begins with a description of how there are not enough types to actually perform a transformation. This makes sense but
Either
is used in the examples here. Just before this section was a the addition of theor
combinator, and before that was converting from usingEither
to usingValidated
.Example from the Transforming data section:
Then later in the
Predicates
sectionValidated
is again used.I propose that
Validated
be used throughout this document, rather thanEither
.The text was updated successfully, but these errors were encountered: