-
Notifications
You must be signed in to change notification settings - Fork 21
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
Release for 2.0 #333
base: main
Are you sure you want to change the base?
Release for 2.0 #333
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thank you @serras 🙌 🚀
content/blog/2024-10-04-arrow-2-0.md
Outdated
between fail-first and [accumulation of errors](/learn/typed-errors/working-with-typed-errors/#accumulating-different-computations). Until now, the latter mode | ||
required using `parZip` and `parMap`, which sometimes obscure the actual | ||
flow of the computation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
parZip
and parMap
are used for parallel operations. Did you mean zipOrAccumulate
here?
content/blog/2024-10-04-arrow-2-0.md
Outdated
parZip( | ||
{ checkOneThing() }, | ||
{ checkOtherThing() } | ||
) { a, b -> doSomething(a, b) } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
parZip( | |
{ checkOneThing() }, | |
{ checkOtherThing() } | |
) { a, b -> doSomething(a, b) } | |
zipOrAccumulate( | |
{ checkOneThing() }, | |
{ checkOtherThing() } | |
) { a, b -> doSomething(a, b) } |
These examples are using context receivers, and/or omitting quite some details. Is it important for us the examples are real-life, and copy-paste able?
usual `async` mechanism, ensuring that all `Deferred` values are `await`ed | ||
once the first one is requested. That means that the previous code behaves | ||
identically to the following, that is, the call `file.await()` implicitly | ||
awaits every `async` defined up to that point. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to add the details why this is important for Raise
, or how not using this could result in hanging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a 1-sentence summary of this I could use?
This PR puts together a bunch of other PRs, to check coherence between them:
Fixes #308