4 ms·
It's the same story in C++, co_await, co_yield. The sole purpose is not to break other people's code.
by Erlangen 6y ago
It's the same story in C++, co_await, co_yield. The sole purpose is not to break other people's code.
- bartvk 6y agoWhenever Swift adds a new keyword, they just add it and break everyone’s code. They do provide migration tools in Xcode though.
- m45t3r 6y agoI think non_sealed would be better than non-sealed though, because AFAIK there used to be no identifiers with hifen before.
- fomine3 6y agoint non, sealed; ?
- gpderetta 6y agoco_await is so bad that co_X has become a running joke in the C++ community.
- kccqzy 6y agoC++ has had two-word keywords since the beginning, static_cast, dynamic_cast, etc. What I truly don't like is C's propensity to add new keywords that begin with an underscore and an uppercase letter. Like _Bool, or _Atomic. (I know the rationale, these can't be used as identifiers due to UB, but it still looks weird to me.)