-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why a Semigroup instance? #35
Comments
Here's a good example of where this is confusing:
I get:
but I expect to get:
|
matthewbauer
added a commit
to matthewbauer/validation
that referenced
this issue
Jun 11, 2019
Previously, a <> b would give success if either a or b were a success! This should not happen when doing validation. We want any errors to be propagated. Fixes system-f#35
matthewbauer
added a commit
to matthewbauer/validation
that referenced
this issue
Jun 11, 2019
Previously, a <> b would give success if either a or b were a success! This should not happen when doing validation. We want any errors to be propagated. Fixes system-f#35
matthewbauer
added a commit
to matthewbauer/validation
that referenced
this issue
Jun 11, 2019
Previously, a <> b would give success if either a or b were a success! This should not happen when doing validation. We want any errors to be propagated. Fixes system-f#35
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
<>
operator on validation values ends up ignoring failures, which seems like something unintended. I discovered this while debugging a validation related bug. Is there a reasonValidation
is an instance ofSemigroup
at all?The text was updated successfully, but these errors were encountered: