Hi! Author here. We are actually planning on removing those literals and allowing applications to extend Roto with their own literals [0]. They should do so with care of course, because indeed adding more literals adds some edge cases. Most applications should be able to get by without any special literals though.
Have you considered collecting all the literals into domains, but ship them by default?
I could, for example, imagine using roto in some of my current work on svg and visuals generation. In which case I'd be greatly helped with literals like "colors", "vec2", "angle" etc. I'd imagine that as long as other literals which I don't need, like an IP address, aren't in the way, it's still greatly beneficial to have a large lib to pick and choose from, around.
Good suggestion! We haven't done that because there's only one domain at the moment but going forward that could be useful.
loading story #48346915
Nice! That sounds like a good change. I'll try to dive a bit deeper through docs once I find some time :)