Pauli Jaakkola

Maybe transformers (and JSON schemas etc.) should be mapped to the schema class (or even instance?) instead of the name? Compilers (and Datomic) get rid of names as soon as...

This could also allow transcoder ("coercer"?) functions that can fail instead of passing invalid inputs through unchanged.

That is not how JITs work. Smaller methods are more likely to get inlined, but larger ones will be compiled too. And the combined methods would be smaller than the...

`parser` is basically `validator` + `decoder` with hardcoded decoders so there is no reason to believe `coercer` would be much more bulky or indirect than `parser` or `decoder`. There is...

1. Is what the Self (and HotSpot) JIT [does](https://bibliography.selflanguage.org/_static/implementation.pdf) (section 6). There is hardly any overhead except when things actually do change.

That's great! And here I thought I was just bragging about having read that JIT stuff. Malli does have a general tension where on one hand we try to precompute...

> So far the lack of this didn't cause any trouble for us but I guess that's just a matter of time. If e.g. one only uses Malli for Reitit...

`tick` pulls in `js-joda`, preferably `malli` would avoid such bloat and opinion.

`encode` and `decode` are 'best-effort'; the standard encoders and decoders return the original value if it did not match the schema. One must first ensure that the input is valid...

Nice point, although one could argue that a base-64 encoded value should not have such a liberal schema. I forget the details but the seqex transcoder implementation is also a...