4 ms·
Trip report: Autumn ISO C++ standards meeting
- saagarjha 6y agoThe additions look very nice :)
- CyberRabbi 6y agoTwo things I’m waiting on in C++: memory-safe “lifetimes” subset and zero-overhead deterministic exceptions, both proposed by Sutter.
- steveklabnik 6y agoI’m not up on the latest here, but did something significantly change with the lifetimes proposal? Last I heard, it was not a subset of the language, and was not attempting to be fully memory safe. (That said I am looking forward to it too; every bit helps!)
- CyberRabbi 6y agoI doubt you’re missing anything, I’m just being loose with my language.
- pjmlp 6y agoIndeed, but it suffices that all major C and C++ static analysers end up supporting it, to the extent that it is possible. On Visual C++ builds, and usage of Eclipe's CDT I always turn as much as possible on. It isn't Rust, but as you say, every bit helps.
- vlovich123 6y agoI'll preface that I'm an outside observer & not a language developer so I may have a skewed sense here, but this caught my eye: > Congratulations to JeanHeyd for C++23’s first language extension, and also for his persistence with this paper – the adopted version is revision 8, and that number and the paper’s change history indicates the level of rigor that can be required to get a feature into C++. Many thanks! Congrats to JeanHeyd for the perseverance & not trying to take away anything from it as it's an accomplishment. I do want to discuss how long changes take to land in C++. For something as relatively straightforward & non-controversial as P0330 that took 8 revisions, how do other languages compare? Do changes to Python, Rust, Go, or Swift take this much effort?
- steveklabnik 6y agoChanges in Rust can take that much effort. It just depends on the change. We’ve never added a directly comparable feature, so it’s hard to say, though I will say that deciding the names of integer suffixes was so contentious it led to one of the few times my work in open source has made me actually cry in real life.
- deleted 6y ago[deleted]
- twoodfin 6y agore: P1679, basic_string::contains, I had always assumed that C++ didn't have Java-like niceties in the standard string class because the C++ library philosophy was to separate algorithms from containers. Doesn't it feel like a failure of the library evolution process that this particular convenience is still valuable enough to add in preference to whatever syntax already falls out of ranges::includes?
- blux 6y agoThis separation was never a hard requirement. For example `std::map` implements `lower_bound` and `upper_bound` as member functions because they can be implemented more efficiently than the general `std::lower_bound` and `std::upper_bound`, at least at the time. The paper itself discusses the member function vs. free function problem: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1679r3.html#42-member-function-vs-free-function http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p167...