-
Notifications
You must be signed in to change notification settings - Fork 75
Post-operator question mark #114
Comments
Hmm - it might be confusing whether |
Mmh, I’m sure that someone somewhere proposed that syntax, and that I explained why I didn’t like it, but I cannot find it... But @ljharb expressed my main objection in fewer words than I would have been able to. Also, someone proposed that in a past poll about preferred syntax, but the option wasn’t very popular... |
Discussed in #61 |
#61 doesn't discuss The reason I think the former is superior to the latter (or |
Overall, the arguments in #61 (which are mostly about how To be fair, you could make an argument that that's worth not having the weird dot in |
Indeed. Syntax has been discussed to death in the past, and we’ve reached rough consensus on the least bad option. I’m closing this issue in order to make clear that, as of now, the proposed amendment has about zero chance to be accepted, in absence of very strong and improbable reason. Thanks for your interest. |
I looked at all the previous alternative syntax proposals, and none of them seem to propose using
.?
,[?
, and(?
as the chaining operators, as I proposed on WICG about three years ago.Wouldn't this make more sense, as the only case where this overlaps currently valid syntax is the
1.?foo:bar
case described in other issues that only propose variations of.?
for the other two operators (which, as noted in those issues, is evitable by not allowing this syntax on numbers)?The text was updated successfully, but these errors were encountered: