I think I might be the progenitor of the {/} syntax in the previous discussions (other people probably thought of it too at some point!) and it’s fun to see the idea actually be brought up for an eventual decision. While I’m fond of the syntax I also understand the apprehension towards this, not based on the exact spelling (people will get used to it), but in the lines of if it’s really necessary since {*()} exists which, could be, or maybe already is, special cased in the compiler. Overall I don’t write enough sets in hot loops (or much Python at all recently) for this syntax to be relevant to me directly. Still, I think it would be good for the SC to make a ruling on this so even if it’s not accepted we can just point to the decision in future discussions.
5 Likes