James M. Lawrence

If you're still following then the new feature will probably be more like the transfer-bindings branch. API is (defvar *foo*) (defvar *bar*) (let ((*foo* 3) (*bar* 100)) (lparallel:transfer-bindings '(*foo* *bar*)...

9bde6fce7 removes the toplevelness of `defpackage`, so you need an `eval-when` there. When the online and offline versions are exactly the same, this guarantees that certain problems cannot occur. That...

The generated file would belong to an ASDF system and updated with one call (maybe a custom ASDF op). I wouldn't do any ad hoc loading as you describe. You...

A package which dynamically adds/exports symbols as loading progresses is rather against established CL convention. The problems from differing `defpackage` forms is a consequence of bucking that convention. This is...

For me the larger concern is the "uncharted territory" of a package scattered across unrelated projects that use the offline setup. The `quickutils` symbols need to be merged appropriately. I...

Consider two projects that have their own util files. Project A uses util X which uses helper H. Project B uses util Y which also uses H. Project A is...

> What do you mean project A is updated? The project shouldn't touch the utils file. Project A will regenerate its util file whenever it adds or subtracts utils. Or...

You might have misunderstood; I said earlier, "On second thought, allowing the user to specify the generated package gives rise to a bloat problem, the very thing quickutils aims to...

What if `utilize` were a local loader? It would serve as a mini `asdf:load-system`, handling dependencies and tracking what was already loaded. No server component; utils are in local files...

What's the simplest thing that could possibly work? All we need is for `utilize` to load a function, given its name. That might entail looking up the corresponding file and...