Gus

When you say normal constructor do you mean tupled ones? Don’t you get tooling support with curried functions as well?

@7sharp9 Fair point, which applies by extension to all non-curried functions and makes me wonder if we should move the focus to tooling improvement, given that most F# functions are...

Using an available user-defined operator will break existing code, specifically => is being used in some projects, for instance Deedle makes heavy use of it. The ambiguity reported by @cloudRoutine...

The problem with `split` alone is that it will shadow (or will be shadowed by, depending on the `open` sequence) FSharpPlus's `List.split` which is a very useful function and probably...

Now that this suggestion was rejected I want to let you know that I did once [an initial port of that library](https://github.com/gusty/FSharp.Data.List), so if someone is interested in taking it...

@dsyme I can share the spec I did for [F#+](https://github.com/gusty/FSharpPlus). Since there the end goal is to have a generic version that works on any collection (Seq, Array, List, String)...

@dsyme here's the set of functions to be added: // split the source on any of the separators specified split separators source // intercalate the separator between the elements intercalate...

@tomcl I'm very aware of the ``concat`` inconsistency, but I don't think ``join`` is a good alternative and will tell you why: - From most Category Theory abstractions ``concat`` comes...

@tomcl I would also prefer coherence with existing F# names over coherence with Haskell or another non-dotnet language. The problem in this particular case is that I haven't found such...

@tomcl Regarding the ``replace`` function, I did apply the same criteria as the ``split`` functions I mentioned in my first message, I mean: > not provide other splitting strategies, not...