Fork me on GitHub
#malli
<
2020-06-16
>
ikitommi10:06:40

with default, malli is all-immutable, with a CLOSURE_DEFINES or JVM Prop setup, the default registry can be swapped out in the user space.

ikitommi10:06:50

allows also really smaller bundle sizes, moved all the defs into defns so closure can eliminate those if needed.

ikitommi10:06:07

@plexus, would that help with your acme-schema sample?

ikitommi10:06:57

also, the options would be default (immutable) or managed (swappable). any suggestions for better names?

plexus11:06:22

yeah I think that would help us

ikitommi14:06:38

even more evil. optional MUTABLE registry constructor, just pass in your own atom.

Vincent Cantin16:06:11

would it be possible to avoid having any mutable registry by having the user define his own API functions defaulting to their own registry?

Vincent Cantin16:06:19

maybe via a macro? (def-malli-api my-registry)

ikitommi17:06:18

that is one approach, and can be done on top of the current api. Not a fan of macros generating functions personally. Need extra work to work with static analysis tools (like cursive) Also, the api should require all the malli namespaces to be complete.

☝️ 3
ikitommi17:06:57

I'll make set-default-regisyry! to throw if the registry swapping is not enabled.