Open amesgen opened 1 year ago
Adding VTAs to the ecosystem is something I was planning to do in the 0.16.0
ecosystem update. And before that happens, we need to specify some guidelines for how to do this, so that whatever design we come up with is consistent across the ecosystem rather than ad-hoc designs that differ across libraries.
If you're interested in contributing to this effort, please type up some initial guidelines on Discourse.
prop
is by far the most frequently referenced function in our codebase. This is an opportunity to pick a shorter name for the combinator. How about on
?
Does your codebase entail a library or application. If the latter, there's nothing stopping you from defining your own prelude with its custom imports to suit your naming preferences.
It's an application, and indeed we do have a P4 for exactly that!
Description of the change Adds a variant of
prop
using VTA (visible type application) which was added in Purescript 0.15.10. Motivation is mainly to save some characters:vs
I chose to also name it
prop
and put it in a new module (as it seems very unlikely that both variants are used in the same project), but also happy to change to other alternatives, like naming itprop'
and putting it inData.Lens.Record
, or simply replacing the currentprop
with the VTA-enabledprop
(would be a breaking change).Checklist: