Open zanieb opened 7 months ago
https://github.com/pubgrub-rs/pubgrub/tree/RPITIT is proving helpful for this — that's what I used in our prototypes to produce the "ideal" message.
Are we still seeing ∅-errors?
We shouldn't be seeing null sets in errors. I'm not sure about the direct dependency conflict thing.
Actually we do show a nullset in this different case:
Example at https://github.com/zanieb/pubgrub/blob/zanie/examples/examples/unsat_direct_dependency_conflict.rs
When the root package depends multiple versions of the same package e.g.
foo==1.0.0
andfoo==2.0.0
, the PubGrub user is required to merge versions via intersection to provide a single package and version pair. This results in a requirement on an empty set giving the unhelpful error message:Ideally the solver would accept multiple versions per package so the incompatibility can be tracked in the derivation tree.
Ideally the reporter would display both provided versions with a note that they are incompatible