4 ms·
A formal technical specification (TS) extension is already being drafted: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3582.pdf https://www.open-std.org/jt
by wahern 1mo ago
A formal technical specification (TS) extension is already being drafted: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3582.pdf https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3582.pdf That's a step up from the usual proposals. I'm not sure what criteria is used to decide whether to first create a TS vs just incorporating a change into the working draft of the next standard.[1] _Defer also seems to be taking the TS route.[2]
1. https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3886.pdf https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3886.pdf
2. https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3928.pdf https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3928.pdf
- pjmlp 1mo agoWell, even if that lands on the official standard, that means C29 as probable release year for C2y, plus adoption of the exact form across compilers to be able to rely on it being available.
- Someone 1mo agoPlus the fact that an implementation that recognizes the new syntax and produces an error whenever it encounters it will be conforming. On such an implementation, the feature is available but useless.
- leoc 1mo agoThere's some discussion of how C29 defer ended up in a TS at https://thephd.dev/c2y-the-defer-technical-specification-its-time-go-go-go#build-wait-are-you-just-making-this-up-entirely-from-scratch https://thephd.dev/c2y-the-defer-technical-specification-its... .