Remix clone Hacker News

In the last few years C# did away with implicit nulls. Nullable and non-nullable object references are disambiguated with T? and T. There are multiple keywords and expressions to further make it nice to work with these. You would be correct to note that there are "nullability holes" in certain edge-case scenarios, particularly around JSON serialization. But other than that it's a pretty smooth sailing.

If you do use C#, you may also want to add <WarningsAsErrors>nullable</WarningsAsErrors> to .csproj too.

▲

cies 5 days ago | parent [-]

I know it's a bit like Kotlin. I heard though that C#'s move still has some std lib bits that are nullable.

	▲	neonsunset 5 days ago \| parent [-]
		The idea is not to never have nulls. It is pointless (ha) - the way to understand T? vs T in C# is like an optional. The entirety of standard library is annotated since long time ago. All new and not so new projects are also null-aware. Pretty much either completely legacy libraries or libraries that explicitly removed Nullable: enable that is set by default for all new project templates do not have those. As I mentioned previously - it isn't perfect, but the level of "good enough" of NRTs in .NET is such that the nullability is a solved problem.