this post was submitted on 06 Oct 2020
1 points (100.0% liked)

.NET

112 readers
1 users here now

founded 5 years ago
MODERATORS
[email protected]
1
Nullable Reference will not protect you, and here is the proof (www.viva64.com)
submitted 4 years ago by [email protected] to c/[email protected]
1 comments fedilink hide all child comments
 

Have you ever wanted to get rid of the problem with dereferencing null references? If so, using Nullable Reference types is not your choice. Do you want to know why? This will be our topic today.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 4 months ago

To make a callout on ! Is ridiculous since it’s literally meant to overwrite the compilers descicion. Ignoring compiler warnings is known to be a bad idea, I mean otherwise there would be no warning at all, right? This is why zero warning policies exist.

Once we get to the point where we think the programmer has no responsibilities at all, we are lost anyways.