Some questions and notes:
How do I instrospect *SOURCE-REGISTRY*? The outlined API only puts
stuff there, but doesn't tell me how to read it.
I would like to be able to mutate *SOURCE-REGISTRY* (even if by
cloning without actual destructive operations) at runtime to isolate
things.
Under which c
I would like to suggest an addition from my experience of working with
colleagues at other companies. I'd suggest that we have a way to
specify files relative to something akin to *load-truename*.
Here's the use case: you work on a large project with an enormous
source code repository, cluttered
Dear ASDF developers,
Rommel and I are currently working on asdf bug #485918,
i.e. a plan for user-customizable persistent configuration of ASDF paths
through configuration files (duh).
https://bugs.launchpad.net/asdf/+bug/485918.
What follows is a detailed plan and several questions.
Ge