Commit 3611d16
committed
fix: Update to have dominance check not be done on same quality
Notably, dominance updates between sort variables were not checking
if the variables were the same. If both were the same and they were
not dominated (e.g. when removing the default Type->s constraint),
then it would loop because it would postpone the dominance check.
It really doesn't make sense though to update the dominance of a
sort variable when adding the reflexive elimination constraint.
The dominant will be the same in both cases, and if there is none,
then it will be dominated eventually when checking with other sorts.1 parent 3e6b224 commit 3611d16
1 file changed
+8
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
168 | 168 | | |
169 | 169 | | |
170 | 170 | | |
| 171 | + | |
| 172 | + | |
171 | 173 | | |
172 | 174 | | |
173 | 175 | | |
| |||
226 | 228 | | |
227 | 229 | | |
228 | 230 | | |
229 | | - | |
230 | | - | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
231 | 235 | | |
232 | 236 | | |
233 | 237 | | |
| |||
292 | 296 | | |
293 | 297 | | |
294 | 298 | | |
295 | | - | |
| 299 | + | |
| 300 | + | |
296 | 301 | | |
297 | 302 | | |
298 | 303 | | |
| |||
0 commit comments