Adapting to changes in C#13

[FreeApophis]

C#13 has some new features which impact Funcky in a fundamental way: we probably want to introduce new API in a 3.x Version, but I think the old API should be phased out and removed in a 4.0 Release.

Changes which might impact Funcky:

params

Sequence.Return

implicit and explicit extensions

ParseExtensions could be static extensions to make the Parse*OrNone functions be visible on the type.

string.ParseInt32OrNone could be int.ParseOrNone()

We could make the Asserts more discoverable by statically extend Assert in XUnit:

• FunctionalAssert.Ok could be Assert.Ok

Sequence could be entirely done as a static extension on Enumerable.

• We could use an explicit Some<T>-Extension-Type as an explicit type to "hide" GetOrThrow()

Some<T> some = option;
var value = some.GetOrThrow();

Let's collect the ideas for new features, adapted features and how to move on here.

[FreeApophis]

Ahh the official links are missing:

https://devblogs.microsoft.com/dotnet/dotnet-build-2024-announcements/#c-13 https://build.microsoft.com/en-US/sessions/689e5104-72e9-4d02-bb52-77676d1ec5bc?source=sessions

[FreeApophis]

AFAIK implementing interfaces is out of scope for C#13 but we could also look if the list pattern support of Option<T> could be extracted into an extension, since it relies on duck typing and not on an interface.

[bash]

I saw the presentation about extensions and got really excited about the possibilities for Funcky 🎉

I bet that we could also do some fun things with properties that we can't right now (i.e. have <Property>OrNone properties on System. objects that turn nullability into options.