Re:Go runtime: 4 years later
by int_19h on Tuesday September 27, 2022 @03:32AM
(#32992467)
The problem isn't null/nil as such, it's when the type system treats null values as legal at compile-time.
But if you look at e.g. Kotlin, or C# with "#nullable enable", it tracks whether a given reference can be null or not. So you write if-else code instead of match, but you have to do that in order to actually do something with a reference.
But if you look at e.g. Kotlin, or C# with "#nullable enable", it tracks whether a given reference can be null or not. So you write if-else code instead of match, but you have to do that in order to actually do something with a reference.