Scott Sauyet
Scott Sauyet
@hitmands: > Apologies for my confusing wording, Not at all. I simply saw what I wanted to see, overlooking an important word. :smile: >> Ramda doesn't have the correct ergonomics...
> I think all this just drives home that you can't design a library like this for (or in) typescript. You can make best effort typedefs which are quite useful,...
@hitmands: But note that there are plenty of other Functors out there. `Function` is a functor parameterized by the return type. Most implementations of `Maybe`, `Either`, `Future`/`Task` and many more...
@hitmands: > I use Ramda, I love it and I'd certainly like to help to make it more robust. Great. I'll discuss it with the group and get back to...
@bxt: I'm thinking that would be more of a fork than a change. I'm quite sure that I'm not alone among the Ramda core team who's not interested in maintaining...
... and how do we make the call about when to do such changes? How widespread does another library / language / tool have to be for Ramda to make...
My thought as to process is that updating the typing file would be a requirement of a *release* process, not a more regular *commit* process. When preparing a release, a...
> I am not sure about type safety not being a pr requirement, this would compromise overall type safety quality and/or put too much burden on a few maintainers that...
Hmm, I wonder what caused this regression. I don't recall any recent work on `applySpec`. I'll have to check this weekend.