You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We hit the following – supposedly unreachable code – in certain cases:
thread 'main' panicked at 'internal error: entered unreachable code: when we get here it means that all candidates have been assigned false. This should not be able to happen at this point because during propagation the solvable should have been assigned false as well.', /Users/tdejager/.cargo/registry/src/index.crates.io-6f17d22bba15001f/resolvo-0.2.0/src/solver/mod.rs:584:53
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
A test has been added to resolvo that recreates the issue #10.
The text was updated successfully, but these errors were encountered:
The original bug was caused by adding a conflicting `requires` clause,
yet failing to detect and handle the conflict. This commit introduces a
clearer separation between: adding new clauses, detecting conflicts, and
handling said conflicts.
Closes#13Closesprefix-dev/rip#75
We hit the following – supposedly unreachable code – in certain cases:
A test has been added to resolvo that recreates the issue #10.
The text was updated successfully, but these errors were encountered: