News for hackers. Stuff that matters.

A comment on Tail-call optimization in C is relatively recent. Parent comment

Re:Tail-call optimization in C is relatively recent by wahern on Monday August 10, 2026 @09:46AM (#49243605)
A formal technical specification (TS) extension is already being drafted: 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

2. https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3928.pdf

[ Parent | on HN ]
Re:Tail-call optimization in C is relatively recent by leoc on Monday August 10, 2026 @10:10AM (#49243932)
There's some discussion of how C29 defer ended up in a TS at https://thephd.dev/c2y-the-defer-technical-specification-its... .
[ Parent | on HN ]
Re:Tail-call optimization in C is relatively recent by pjmlp on Monday August 10, 2026 @09:57AM (#49243738)
Well, 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.
[ Parent | on HN ]
Re:Tail-call optimization in C is relatively recent by Someone on Monday August 10, 2026 @10:11AM (#49243953)
Plus 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.

[ Parent | on HN ]