Description
Context: haskell-unordered-containers/hashable#310 (comment)
From what I understand, the solver has a backtracking behaviour for flags and deprecation statuses, where it will switch flags to see if a particular combination is best suited for what the user has (sometimes unknowingly) asked.
If flags can be kept to a certain value with a freeze file, it's not the case with (transitive) dependencies that we know for sure don't want based on their deprecation status.
It would be interesting to explore the option of having a strict solving mode, optionally enabled of course, which give more expected results in terms of solver errors (“you tried to depend on a deprecated release or package”) rather than an unexpected solver success which nonetheless brings an unwanted dependency.
Activity