A few proposals from the C standards committee

["Paul E. McKenney" <paulmck@kernel.org>]

Hello!

On the perhaps unlikely off-chance that any of this is of interest.

							Thanx, Paul

------------------------------------------------------------------------

List of proposals with clickable links:

https://www.open-std.org/jtc1/sc22/wg14/www/wg14_document_log

N3089 _Optional: a type qualifier to indicate pointer nullability
	Proposes _Optional to tag pointer parameters such that
	dereferencing the pointer without first checking for NULL gets
	a compiler warning.
	https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3089.pdf

N3190 Extensions to the preprocessor for C2Y
	Proposes a number of macros, including things that return a
	count of their arguments.
	https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3090.htm

N3194 Case range expressions
	No fewer than 421 files in the Linux kernel use the "..." syntax,
	as in "case 1 ... 3", but there are other syntaxes...  So they
	are proposing "::" instead.  My guess is that "..." won't be
	going away anytime soon.

N3195 Named loops
	Placing a goto label before a loop allows a break/continue to
	target that loop in case of nesting.

n3203 Strict order of expression evaluation
	I do like it.  The 1980s were over a long time ago.

N3199 Improved __attribute__((cleanup)) Through defer
N3198 Conditionally Supported Unwinding
	The Linux kernel is starting to use __attribute__((cleanup))
	via guard(), with 40 files making use of this.	It is not clear
	to me whether or not either of these proposals would be useful
	to the Linux kernel.

N3201 Operator Overloading Without Name Mangling v2
	I have seen Linux-kernel interest in *function* overloading, but
	not in operator overloading.  Nevertheless...

	The trick here is to associate a given operator with a function,
	so that the name-mangling becomes essentially a manual operation.