C# in Unity 2026: Features Most Developers Still Don’t Use
Posted by KwonDarko@reddit | programming | View on Reddit | 3 comments
Posted by KwonDarko@reddit | programming | View on Reddit | 3 comments
manifoldjava@reddit
Nice breakdown explaining why properties, tuples, etc. are useful.
Properties in particular are often misunderstood with the "Just use fields" crowd, which is unfortunate. Kotlin, in my view, got it right by making properties built-in behavior with member-level
valandvardeclarations. Brilliant design choice. Kotlin also leverages properties as state abstraction to make lazy values and delegation extensions of this built-in behavior. Would be awesome if C# would follow Kotlin's example:Using tuples for multiple return values is also an underused strategy. Although I think C# should extend
varcoverage to method return types for this, that or provide a separate keyword for it, like manifold'sauto(Java):nekokattt@reddit
in the latter case it isn't much more work to have a record type that handles the same rough case.
manifoldjava@reddit
It’s not, but it’s more idiomatic boilerplate I’d rather not write.