We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
attemptF
Hi,
I have encountered an inconsistency with the order of type parameters in the attemptF method within which could potentially cause confusion.
final class SealedFAOps { def attemptF[ADT, B] } // When using attemptF: attemptF[FooResult, Unit]
sealed trait Sealed { def attemptF[B, ADT1 >: ADT] } // When using attemptF: attemptF[Unit, FooResult]
The text was updated successfully, but these errors were encountered:
Fixing #204
2da4563
Eval refactor, fixing bugs in evaluation order (#217)
6f436ba
* Refactoring evaluation with new computation model. * inspectF * Small doc update * Fixing *semi*. * Fixing leftSemiflat*ap * Eval refactor continued (#218) * WIP with tailRecM * Cleanup * Working version. Some documentation. Dependency updates. * Missing build changes. * Website 2.12 update. * Update scalafmt-core to 3.7.17 (#216) * Update scalafmt-core to 3.7.17 * Reformat with scalafmt 3.7.17 Executed command: scalafmt --non-interactive * Add 'Reformat with scalafmt 3.7.17' to .git-blame-ignore-revs * Update sbt-mdoc to 2.3.8 (#213) * Update sbt-jmh to 0.4.6 (#211) * Update sbt-scalafmt to 2.5.2 (#209) Co-authored-by: Łukasz Sowa <contact@luksow.com> * Update sbt-ci-release to 1.5.12 (#190) Co-authored-by: Łukasz Sowa <contact@luksow.com> * Update sbt to 1.8.3 (#191) * sbt bump * Fixing #204 * Solving #205. --------- Co-authored-by: Łukasz Sowa <contact@luksow.com> Co-authored-by: Scala Steward <43047562+scala-steward@users.noreply.github.com>
No branches or pull requests
Hi,
I have encountered an inconsistency with the order of type parameters in the
attemptF
method within which could potentially cause confusion.The text was updated successfully, but these errors were encountered: