[Amendment] SE-0296: Allow overloads that differ only in async

This question hasn't been answered, but I suppose that that proposal reviews are not discussions. As such, I'll say this another way:

I am -1 on the proposal unless we extend this to the throw effect, if we add both then I am +1.

Rationale: I believe that it is important to allow async overloading, but even more important to keep the language consistent about how it handles effects. Inconsistency makes the language more complex and makes future things more difficult to add.

Is there any disadvantage to allowing overloading on throws?

-Chris