Jon Pretty
Jon Pretty
Todo: - [x] compile, instrument and run benchmarks - [ ] ensure benchmark modules are run isolated - [x] automatically add dependencies - [ ] offer configuration for benchmark modules
When a plugin is built from source using Bloop, the resultant classfiles reside in a temporary directory, created by Bloop. Downstream modules, however, are configured to use a plugin whose...
If a module hasn't changed since it was last compiled, it shouldn't be run a second time if it's deterministic. This may require discovering or querying Bloop to determine if...
When running completion continuously, changes to the source files will be noticed, but changes to the structure of the build won't be. We should have a global object which continuous...
It should be possible to mark application and benchmark modules as "isolated" using an `--isolated`/`-I` flag. This would configure the modules to run only when there's nothing else running.
Projects have a license which is specified as a string (with autocomplete suggestions from a list). But this isn't very robust or useful. Instead, Fury should store a reference to...
Fury uses several different colors for output, which are designed to indicate the nature of some identifiers. But several colors are reused for multiple different semantic purposes, while there are...
Some integration tests fail sometimes, and sometimes succeed, such as the old `scala3` test. Non-deterministic features aren't desirable, but we should have a place for tests which might succeed or...