Have you ever used the Nullable annotations setting in your C# projects?
I use it in Multi-targeting projects for older Frameworks like .NET 4.8. You avoid a lot of unnecessary warnings. For example when using string.IsNullOrEmpty().
#csharp#sdk#nullablereferencetypes
It hurts me when I open a codebase, #nullablereferencetypes are turned on in some places or not even turned on, and there are question marks scattered all over the place but no code rules turned on.
There has been massive communication failures with NRT
#dotnet#csharp
Смею заметить, что система типов .Net бессмысленно сложна, и проще и лучше со временем не становится (исключение - NullableReferenceTypes). И в этот переломный момент они позволяют SPJ уйти.
.@jonskeet thx for convincing me of "why it is implemented this way" on #NullableReferenceTypes in #csharp, I was very much opposed in the beginning.
I do still use it in combination with a library that includes the Option<T> and Either<L, R> types. youtube.com/watch?v=1tpyAQZF…
At some point it might be wise to stopp adding operators to undo the harm of history and instead choose another language. Fortunately f# runs on the same CLR. In other news; for C# version OneMoreTry I predict the introduction of a mutable type operator ! #nullablereferencetypes
YAML builds are really nice. I've almost completely converted dotnet/roslyn CI over to YAML based builds. Currently testing it out on the features/NullableReferenceTypes branch. Expect to go to master early as next week