First in C#

[Real Troll]

Microsoft has for the very first time Introduced "Nullable Reference
Types in C#" Apparently everybody knew about this since 1965 but nobody
thought of implementing it!!!!! Now this is Microsoft speaking.

<https://blogs.msdn.microsoft.com/dotnet/2017/11/15/nullable-reference-types-in-csharp/?utm_source=vs_developer_news&utm_medium=referral>

[Chris Ahlstrom]

Real Troll wrote this copyrighted missive and expects royalties:

I always get a chuckle out of languages that purport to clean up the
"messes" of C and C++, and replace them with something even more
problematic.

--
Good news. Ten weeks from Friday will be a pretty good day.

[Öö Tiib]

On Monday, 27 November 2017 12:35:35 UTC+2, Chris Ahlstrom wrote:
> Real Troll wrote this copyrighted missive and expects royalties:
>
> > Microsoft has for the very first time Introduced "Nullable Reference
> > Types in C#" Apparently everybody knew about this since 1965 but nobody
> > thought of implementing it!!!!! Now this is Microsoft speaking.
> >
> > <https://blogs.msdn.microsoft.com/dotnet/2017/11/15/nullable-reference-types-in-csharp/?utm_source=vs_developer_news&utm_medium=referral>
>
> I always get a chuckle out of languages that purport to clean up the
> "messes" of C and C++, and replace them with something even more
> problematic.

The languages that add "optional" or "nullable" support into core
language win the opportunity to design it in diagnosable and
optimizable manner.

The library solution like 'std::optional' of C++ has its inefficiency
inbuilt. For example 'optional::value_or'. It can't leave its argument
unevaluated when this has value and so it is innately inefficient.
People have to use 'some_optional ? *some_optional : argument()'
instead of 'some_optional.value_or(argument())' always.