oh, thanks, I'll add links to cheatsheet and quickstart pages to the README, it really makes sense!
As for the magic-stuff, I was contemplating designing the API with this approach, but I changed my mind because it would be difficult to tell which python expressions are evaluated at the moment of a conversion definition AND which in the compiled code.
However if we imagine this "magic" API, then it could be even closer to normal python code:
m["key"].some_method(...)
which would resolve everything under the hood.
===
as for the collapsable generated code examples -- I've jotted down :)
As for the magic-stuff, I was contemplating designing the API with this approach, but I changed my mind because it would be difficult to tell which python expressions are evaluated at the moment of a conversion definition AND which in the compiled code.
However if we imagine this "magic" API, then it could be even closer to normal python code:
which would resolve everything under the hood.===
as for the collapsable generated code examples -- I've jotted down :)