Stefan Bertels
Stefan Bertels
This is an addition to #720. I think it's less important than `IComparer` but still has some use when dealing with non-LanguageExt code (like LINQ extensions, System.Interactive ...). I've seen...
There is a bug in .Distinct() when a custom comparer is used. PR includes test and fix. Bug is that default GetHashCode is used -- this is not valid with...
After updating to LanguageExt 4.x I ran into a problem caused by implicit convertion from `string` to `Error` because I have a method with two overloads and both overload types...
I think there is a bug somewhere in `Map` for net5.0. Everything is fine for netcoreapp3.1. Note: I found this using property based testing and can recommend this (especially for...
Just checking https://github.com/louthy/language-ext/releases/tag/3.3.34. Question 1: Should/could generated classes be `partial` or otherwise be more customizable? I read that you decided against this but sometimes could be nice to add e.g....
Using `[Hashable(...)]` in `[Record]` results in runtime error. Found this bug because I didn't use `[Hashable(...)]` but just `[Eq(...)]` and `[Ord(...)]` resulting in different hash codes. --- IMHO it's error-prone...
Files containing '[Record]' classes (codegen) without `using LanguageExt;` failed to compile.
`Fin` has wrong type in `IEnumerable`. Side effect of the bug: XUnit will run into stack overflow if `Assert.Equal()` is used (see test). Workaround: convert to `Option` with e.g. `myFin.ToOption()`
1. [BUG] Tests shows that notFollowedBy reports wrong position. Fixed. 2. notFollowedBy did output result of p. This might be something different than input string and therefore might hide the...
I just had to locate a bug regarding decimal number parsing (decimal separator issue). CsvHelper is working fine, but I wrote a simple test to rule out the possibility for...