Ryan Schmukler

+1

Just pinging on this as well! I'd love to see this land in alpeh.

My leaning on this would be to keep them separate. A few questions that come to mind as "undefined" behaviors if we do merge them: 1) What happens with something...

Personally lean towards it being property-based. Overloading `:closed` is an interesting idea.

I don't have strong opinions on this but another thing worth considering is the interaction with things like `mu/merge` and whether it is useful (or bad) to have the frequencies...

I personally lean toward using a shared implementation with a potentially different `:type`. I think the predicate schemas are worth keeping as I think there's some appeal to them for...

Upon further thought, while the solution proposed in number 1 solves the issue for malli, it still makes transformer authors have to register the duplicate keys (eg. `'int?`, `:int` and...

I can't seem to find the issue that was discussing this - but I'd like to echo sentiment seen elsewhere that this fundamentally seems like an alternative syntax for a...

Just linking this here for consideration: https://github.com/henryw374/cljc.java-time I've done no research, just wanted to make sure it was known to exist for when this is implemented.

Also worth checking out http://juxt.pro/tick/docs/index.html