Allow (...) around throws alternatives #13823
Conversation
| def foo4(i: Int)(using CanThrow[Ex1])(using CanThrow[Ex2]) = | ||
| if i > 0 then throw new Ex1 else throw new Ex2 | ||
|
|
||
| //def foo5(i: Int)(using CanThrow[Ex1 & Ex2]) = // does not work: no capability aggregation is supported |
There was a problem hiding this comment.
Originally in the reported issue there was (using CanThrow[Ex1 | Ex2]) instead of (using CanThrow[Ex1 & Ex2]) and we need a separate negative test to check the error message in this case because it's wrong now. It still suggests adding (using CanThrow[Ex1 | Ex2]) clause to the method almost it's already there and it's not supposed to work.
In case of (using CanThrow[Ex1 & Ex2]) we could also try to make the compiler give a better message explaining why this might be wrong
There was a problem hiding this comment.
OK, I'll take a look.
There was a problem hiding this comment.
It'd be nice to have throws E1, E2 which will mirror the new extends Class1, Class2 syntax but probably off topic.
There was a problem hiding this comment.
That would lead to ambiguities.
Fixes #13816