fp.

I'm glad to finally see this making it's way into C#. Not so much because I want to use unions purely in C#. But because I want to be able to define them when interfacing with other languages.

Quarrelsome•15m ago

I mean yes, but also: uh-oh. I'm looking forward to reading some code that is even more confusing than the code I'm already reading.

Not entirely convinced that I see the usecase that makes up for the potential madness.

vips7L•11m ago

Union/sum types are generally a good thing. Even Java added them. They tend to be worth “the madness”. Now the rest of all the crazy C# features might be a different question.

dgellow•9m ago

What features do you see as crazy?

munchler•6m ago

Unions are simpler than subclasses and more powerful than enums, so the use cases are plentiful. This should reduce the proliferation of verbose class hierarchies in C#. Algebraic data types (i.e. records and unions) can usually express domain models much more succinctly than traditional OO.

moomin•13m ago

AFAICT, this means you won’t be able to define Either<string, string>, which is definitely a thing you sometimes want to do.

throw1234567891•5m ago

but can you define T1 and T2 of string, then use Either<T1, T2>?

le-mark•11m ago

I used to see some excitement around .net core several years ago. I haven’t heard or seen much in the wild. Is anyone using .net on systems other than windows nowadays?

dgellow•8m ago

It’s huge in the game dev world, with Unity and Godot. .net also had a reasonable community on mobile for a while thanks to Xamarin, but I cannot imagine that many people using it for new mobile projects in 2026 (outside of game dev I mean).

It’s a very decent language and runtime, I wish it had more market share in the startup world.