Remove redundant ReturnIfAbrupt shorthands#1225
Conversation
|
I'm doing this since I guess this shouldn't collide with #1224 (comment):
Just want to make sure this is in the right direction since I'm not super familiar with ReturnIfAbrupt. Especially:
Is this needed to do this cleanup? |
|
Yes, I think this is in in the right direction. Basically:
I think we should be sure to do all of these at once, as otherwise it's a bit confusing.
I'm not sure; I welcome your input or that of the other editors. Without the header, the situation is a bit confusing, because you can only know whether an abstract op returns a completion or a bare value by inspecting the call sites. (I.e., if all call sites use ?/!, it's a completion. If all do not, it's a bare value. If it's a mix, that's a spec bug.) It seems relatively easy to get confused. However, it might be worth thinking about the world post-#1224, to avoid wasted effort. I'll comment over there with some ideas. |
See #1224
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff