docs VS CSharpFunctionalExtensions

MS docs ar now on github. Licence lists "CC-BY-4 and MIT licence found" https://github.com/dotnet/docs/tree/main

Yeah, I saw that devdocs and the like don't include what was previously not cross platform and not popular for linux guys: C#, msbuild.

This ability to nest object/collection initializers is not documented TMK and if you feel it is you could update this nearly 4 year old ticket requesting it be documented: https://github.com/dotnet/docs/issues/12979 .

To be like, really pedantic, C#'s foreach will perform an implicit typecast in some scenarios, which can cause the enumeration to throw an InvalidCastException when it hits an item that can't be cast to the specified type (in this case, ShadowCaster2D).

Hey, I am considering adopting the Result pattern in my codebase. Wanted to get some opinions from someone who has experience with it: should I start with language-ext or FunctionalExtensions?

I like both of those libraries but my favorite is CSharpFunctionalExtensions.

This very popular library CSharpFunctionalExtensions does not add the “Async” suffix because:

Something that also has types to handle such cases is https://github.com/vkhorikov/CSharpFunctionalExtensions

CSharpFunctionalExtensions Really great, this is all you need

https://github.com/vkhorikov/CSharpFunctionalExtensions is a small library that has a really nice Result type included, which allows implicit converisons.

If you think your Kentico Xperience site might benefit from returning failures and using the Result monad, checkout the CSharpFunctionalExtensions library and my library-in-progress XperienceCommunity.CQRS. It codifies these patterns for data retrieval and integrates cross-cutting concerns like logging and caching.

https://github.com/vkhorikov/CSharpFunctionalExtensions - a package with ready types and functions :)