avalonia-dotnet-templates VS OneOf

Avalonia does Just Work from F#; it even has `dotnet new` templates for F# (https://github.com/AvaloniaUI/avalonia-dotnet-templates).

That said the ViewLocator was removed intentionally from the templates: https://github.com/AvaloniaUI/avalonia-dotnet-templates/issues/177

The plugin only adds a live previewer similar to that of WPF. To create a new avalonia project, you need to install the dotnet templates which can be found here: https://github.com/AvaloniaUI/avalonia-dotnet-templates

Here is link number 1 - Previous text "CLI"

You could use Avalonia. This is xaml crossplatform and will be better supported than wpf. You can get the templates for dotnet new Avalonia. It's xaml, fast templates and there is a designer op github, can't fidn it atm. Some examples

OneOf

Inclusive, para suportar esse tipo de funcionalidade, foi criada a biblioteca OneOf: mcintyre321/OneOf: Easy to use F#-like ~discriminated~ unions for C# with exhaustive compile time matching (github.com)

Then I found discussion of the OneOf package, and then found some simpler Result code. I tried using that code but I found the use of Match and lambdas meant I couldn't simply break out of the loop in my example.

Until that feature lands there's this https://github.com/mcintyre321/OneOf which is pretty nice.

Yep, it's called result pattern, aforementioned above. There was two highlighted implementations - OneOf, FluentResults.

No he didn't. He made a video of the OneOf library. Not this one.

We already have OneOf https://github.com/mcintyre321/OneOf I've used it in Production multiple times and it's an awesome way to keep everything strongly typed and eliminate null reference exceptions.