Things are copyrighted by default. Just because something doesn't have a license on it (like, for example, a piece of code from a WG21 paper) does not mean it's in the public domain. Quite the contrary, in fact.
Just saying.
So far my favorite part of a certain recently announced programming language is how its documentation casually declares the digit grouping systems used by a few billion people unconventional.
TC retweeted
I said a couple weeks ago that I would write a new #cpp post explaining why T* makes for a really poor optional<T&> despite superficial similarities.
Here is that post: brevzin.github.io/c++/2021/1…
Fun fact: git says the zip paper added 2915 lines to the working draft's sources and deleted 124.
The 27 other papers adopted at the October plenary combined added 2638 lines and deleted 1041.
TC retweeted
Because when you show people nonsense code and you say ARE YOU SURPRISED BY THIS?!??!?! People tend to be surprised by this, and that definitely demands change RIGHT NOW.
open-std.org/jtc1/sc22/wg21/…
Achievement unlocked: write a piece of wording so subtle that no implementer got it right on their first attempt.
I guess this explains the flood of new accounts today...
Top 10 C++ Resources You MUST Know About
youtu.be/eSDVVrjFh54
(These will change your life! 🤣)
Me (LWG3530): We shouldn't force implementers to jump through hoops to support pathological types.
Also me (P2162R2): Here are some pathological types. Make sure your implementation support these.
I wrote a PR that would have made pair know about allocators.
Then figured out a different way to fix the issue that doesn't require changing pair.
Crisis averted?
Look like the special snowflake found cppreference. I'm probably not going to be as patient as Jonathan...
This Post is from an account that no longer exists. Learn more
Doctor, it hurts when I do this...
It's en.wikipedia.org/wiki/C17_(C… now. And nobody asked me to explore alternative titles either.