4 ms·
I think that would violate this rule > The computation must happen at application runtime, i.e. you cannot process the measurements file at build time (for ins
by yellow_lead 3y ago
I think that would violate this rule
> The computation must happen at application runtime, i.e. you cannot process the measurements file at build time (for instance, when using GraalVM) and just bake the result into the binary
- e63f67dd-065b 3y agoAh I didn't actually follow the link to the github repo. I don't think that percludes pre-processing the input into something that needs no parsing, however, or to spawn a background daemon that prefetches everything in the right order. The first run is indeed runtime, not build time, so technically I think I still count with pre-computation, sending that to the daemon (or just stashing it somewhere in /tmp, or even crazier patching the jarfile), and just printing it back out on the second run onwards.
- robertlagrant 3y ago> I don't think that percludes pre-processing the input into something that needs no parsing Why not preprocess it into a file that contains the answer? (-: My read of the description was just: you're meant to read the file as part of the run.
- gunnarmorling 3y agoYeah, and I'd count caching results between runs into the same category, i.e. against the spirit of this challenge. Folks should keep in mind that the goal is to learn something new, rather than "winning" by cheating the rules.
- cm2187 3y agoThough the caching done by the OS (I/O for instance) is fair game
- gunnarmorling 3y agoYes, exactly. Retrieving the source data file from the page cache != storing and reloading precomputed results.