language-ext VS Pry

You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).

Language-Ext is my personal favourite, but it can be a bit overwhelming for beginners due to its extensive feature set

> but I just want something closer to Scala, but for .Net

That's what I'm working toward with my language-ext library [1]. Obviously more support for expression based programming would be welcome (and higher kinds), but you can do a lot with LINQ and a good integrated library surface.

[1] https://github.com/louthy/language-ext

Definitely a fan of option types, I wonder this library has anything over the C# library language-ext which also has an Option type?

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?

> [1] https://github.com/louthy/language-ext

Cool library. I've had a few of these patterns in my Sasa library for years, but you've taken it to the Haskell extreme! Probably further than most C# developers could stomach. ;-)

You might be interested in checking out the hash array mapped trie from Sasa [1]. It cleverly exploits the CLR's reified generics to unbox the trie at various levels which ends up saving quite a bit of space and indirections, so it performs almost on par with the mutable dictionary.

I had an earlier version that used an outer struct to ensure it's never null, similar to how your collections seem to work, but switched to classes to make it more idiomatic in C#.

I recently started sketching out a Haskell-like generic "Deriving" source generator, contrasted with your domain-specific piecemeal approach, ie. [Record], [Reader], etc. Did you ever try that approach?

[1] https://sourceforge.net/p/sasa/code/ci/default/tree/Sasa.Col...

[2] https://sourceforge.net/p/sasa/code/ci/57417faec5ed442224a0f...

languageext supports linq for its monads and I kinda love it. The challenge is convincing my colleagues. 😅

language-ext supports it and it's pretty dang cool.

I can only recommend c# language extensions library https://github.com/louthy/language-ext

that's surprising considering `pry`[1] is such an amazing debugger IMO.

[1] https://github.com/pry/pry

All of my recent tutorials and projects were primarily managed using the default Ruby REPL, irb, and I must say it's been nothing short of amazing. However, what ultimately prompted me to switch to Pry was its offering of better defaults. But what exactly does that mean? Let me demonstrate:

For older versions: Pry Gem

To do that, I would install `pry` into your rails project and then use it look around right before your test fails.https://github.com/pry/pry

This means I can be editing a shell script and easily inject arbitrary regions into a shell buffer for immediate testing (point never leaves the window where I am editing, and I can view the shell output in an adjacent window). This is similar to what Robe does with Pry within an inferior Ruby process using comint.

https://pry.github.io/ - also a lot of features from Pry have made it into the default IRB these days, but I still use pry. I don't know the equivalent commands in IRB.

For debugging, while not multi-threaded, to my knowledge, is the pry gem for debugging. There are a few different flavors, for instance, my favorite is pry-byebug.

Github Link : https://github.com/pry/pry