david cao

There are definitely several parts of elba that would be good candidates for separating out into their own packages (not only the resolver, but also semantic versioning, etc.). I'll look...

I've created repos for elba's [semantic versioning constraints](https://github.com/elba/semver_constraints) and [implementation of pubgrub](https://github.com/elba/pubgrub). The former has already been implemented, while the latter hasn't. @yawpitch: the reason this crate exists is since...

1. I think it'd make sense to represent the Retriever as a trait - we need a central source to get information about packages from. Pubgrub doesn't really care about...

I've had difficulties with renewing this domain, so we might have to transition to a different one in the near future

Yo! Sorry about my absence lately - life has made it hard to find free time and it's been a while since I properly worked on this codebase. The end...

@andylokandy Sounds good! We can start the reimplementation on a new branch (`ng` or `idris2` or something)

@bigs I think as far as a minimal feature set goes, pretty much all we need is fetching/cloning, resetting, and dealing with submodules (if possible)

@bigs Thank you so much for your work on this! It's greatly appreciated :) Right now, unfortunately we don't have a central design document for what elba-in-idris-2 would look like....

Fixing this would probably require a pretty big shift in how elba treats packages - elba doesn't keep track of if a specific target changes, only if an entire package...