Skip to content

Dependency loading #6

@timmc

Description

@timmc

I'm considering making some major changes to liverepl in response to pain points I've found while using it at work. The most important one is the lack of dependency loading at runtime. For example, we don't want to ship tools.trace with our servers, but if we need to inspect a misbehaving server, liverepl doesn't have a way to introduce that lib as needed. I'm thinking of loading both by Aether coordinates and by filesystem path.

Is this a feature you'd be likely to accept a PR for, or should I look at ways of making this feature more separable? (E.g. add support for loading just one additional dependency at liverepl launch, and that additional thing could be used by the user to bootstrap to a dependency loader.)

If you want to chat with me about it more synchronously, I'm always on freenode IRC as TimMc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions