Jurgen J. Vinju
Jurgen J. Vinju
ok yes; understood. I'm expecting an "extended subset" of the Caffeine features and I'm not sure where the boundaries are. In particular the asynchronous backroom serialization to disk; I'm not...
Still there could also be other factors causing this slow-down: * Java 11 JRE - a big change in the context * GitHub Actions hardware/virtual machine configuration is out of...
3 hours or 2 hours; https://github.com/usethesource/rascal/actions we should be able to explain the differences between these last few runs with big differences in efficiency.
Yes that too. Rodin just found the cause of that. No tpl file was ever reused.
Is there any evidence that simply calling isDirectory is not just as fast? the Java file system API needs a separate call as well (we call `String[] File.list()` at the...
* If this has benefits, then it means we have a slow resolver anyway (let's say in an unindexed jar file), and we'd better resolve that then hide it behind...
* what I mean is that if we have missed implementing a cache then we should fix that instead of tupling list and isDirectory. * if stat and list need...
:-) good point! got confused.
Unless we have measured this to be a real performance issue, I'd rather close it and focus on other things. Makes sense?
I think we have to think about this slowly and carefully. Out loud: * The JSON-bridged filesystems are a thing on their own but they should not complicate all the...