Re:C-for-all: Extending C with modern safety and productivit...
by thechao on Wednesday December 04, 2019 @08:20AM
(#21701887)
Right? I keep thinking that the first place to start on a better C is to ask what needs be removed — not added. Once the “bad parts” are removed, what ergonomic features need be added back in?
For starters: implicit coercion is out; weak type aliasing is out; automatic binary serialization of aggregate types is out; etc.
For starters: implicit coercion is out; weak type aliasing is out; automatic binary serialization of aggregate types is out; etc.