-
Notifications
You must be signed in to change notification settings - Fork 23
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
New compilation failure when for-loop and match both used in async (after upgrading 0.9.5→0.9.7) #56
Comments
real-life code where I worked around it: ScoreUnder/canti-bot@a92a67c |
ScoreUnder
changed the title
New compilation failure when for-loop and match both used in async
New compilation failure when for-loop and match both used in async (after upgrading 0.9.5→0.9.7)
Jan 31, 2022
Hi, thanks - will look. |
caused by scala/scala3#14393 |
It's with 0.9.7 and dotty 3.1.1. The issue still does happen on the latest master too (d82a36a). Thanks for looking into this |
rssh
added a commit
that referenced
this issue
Feb 1, 2022
rssh
added a commit
that referenced
this issue
Feb 1, 2022
should be fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found a compile-time error in my project which I bisected to one of these commits in dotty-cps-async:
I had to skip some which either would not build on my machine or which did not run in my project for other reasons (class version mismatch).
I have tried to minimise the code which triggers the bug, but here are a few pieces of code that all trigger it:
Import statements
(Pick whichever is the simpler example for your internals)
Notably, removing the foreach-loop (which is not using
await
) somehow makes it work again, as does collapsing thematch
. In the 3rd example, if you extract the argument toawait
into a variable and await on the variable instead, that works too.The text was updated successfully, but these errors were encountered: