Stanisław Barzowski

Renamed the issue, because while the original proposal was rejected, the follow-up is pretty good.

@arlyon This is not really related to this feature. This issue is about a more convenient way of defining `local` variables. Please create a separate issue and move your comment...

@nikolay It's not about the stdlib, it's about the language. Hermiticity is a core principle of Jsonnet. The output shouldn't be affected by the environment. Jsonnet code shouldn't jump around...

Unless I'm missing something providing an object with directory contents (possibly recursive), and have imported directories specified in the commandline would also work and be a bit easier to control....

> > but doesn't let jsonnet jump around the whole filesystem > How this would be different in term of Hermiticity ? The caller of jsonnet command has control over...

> As long as the imported strings are not interpreted (parsed into Jsonnet Code?) it is just data in bytes after all. I agree. I would be on board with...

@Jezza Yes, that's basically the idea. There are still some complications, though: 1) There might be further directories, so it should probably be recursive. 2) We support importing from things...

Yes, that was the initial motivation for having them this way. I saw bugs resulting from this decision more than once. Union, intersection and difference already require O(n) time. The...

That's really cool. I'll collect the pointers to the relevant parts of the code soon. We'll need it to do it for both C++ and Go implementations, but even the...

> If I'm not mistaken, we may need to change or introduce a new way of reading files entirely? No. Fortunately, we already have the importer API which handles arbitrary...