[nurettin]

Well I should question whether if you are used to working with teams or developing projects others started, but I'm too nice for that.

I've had my own share of ICEs and patches back in gcc3 days where Debian mailing lists were being used as a gcc issue tracker :-) and these days you just fork and work from there. And if people really need your patches, they will integrate it willingly. No need to "get through" anyone.

If you need some confidence boost, start off with reading semi-old patches from other contributors. That will immediately take you to the cogs of the machinery so to speak. Also, debugger is your friend. I hope you have one for your parallel VM.

I maintain 15+ year old delphi code bases as a profession, so I guess your rant just flew out of the window for me. The "tests passed all green checks" insta-gratification is a lost memory. The freedom to implement whatever you want is kinda constrained but still there.

[oblio]

Ok, let's assume that you're willing to go through 10 feet of snow for hours, uphill both ways.

To really change C, you need to at least get your changes in clang, not only in gcc. And let's not even talk about msvc. Or God forbid, actually creating a new standard version.

[nurettin]

I definitely agree that your perceived goal of "changing C" is not attainable. And it is not something I proposed. You could add a flag to a fork of a compiler/toolchain and if it is useful, others will eventually catch on.

[oblio]

I know about "instant gratification" being kind of bad, but even your moderate proposal is something like "gratification in half a decade" :)