Tolerate access to RaiseAccumulate.Error values in accumulating
#3813
+110
−108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Kover Report
|
serras
reviewed
Dec 15, 2025
Comment on lines
+40
to
+42
| val x = accumulating<Int> { raise("hello") } | ||
| val y = accumulating<Int> { raise("bye") } | ||
| x.value + y.value |
Member
There was a problem hiding this comment.
Why are these tests changed? We need to ensure that using by works as expected here
Collaborator
Author
There was a problem hiding this comment.
by can't be supported in this PR, annoyingly. This is the biggest reason why I've kept it a draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal is to allow usage patterns where
accumulatingvalues can depend on otheraccumulatingvalues.I'm not super happy with this yet. It doesn't play well with property delegation (because you can't have context parameters on
getValueyet, and even then, the design of that feature is unclear).