News for hackers. Stuff that matters.

A comment on The Cost of a Closure in C. Parent comment

Re:The Cost of a Closure in C by pjmlp on Thursday December 11, 2025 @10:38AM (#46232714)
The author contributes to ISO C and ISO C++ working groups, and his latest contribution was #embed.
[ Parent | on HN ]
Re:The Cost of a Closure in C by steveklabnik on Thursday December 11, 2025 @11:22AM (#46233351)
Not just that, the author is the Project Editor for WG14.

This doesn’t mean that it’s impossible to make mistakes, but still.

[ Parent | on HN ]
Re:The Cost of a Closure in C by uecker on Thursday December 11, 2025 @12:31PM (#46234352)
It means he can edit LaTeX. Of course, JeanHeyd is very qualified, but being project editor for an ISO standard does not require this.
[ Parent | on HN ]
Re:The Cost of a Closure in C by steveklabnik on Thursday December 11, 2025 @12:47PM (#46234578)
I mean, you're closer to the committee than I am, but while that is true in a literal sense, I'd assume that you all would not let someone who knew how to edit LaTeX but not know anything about C hold that position.
[ Parent | on HN ]
Re:The Cost of a Closure in C by uecker on Thursday December 11, 2025 @03:14PM (#46236533)
Assuming we have some choice. Not many people volunteer their time to this work, which is quite a lot and not much fun. Companies also do not invest a lot of resources into C.
[ Parent | on HN ]