diff options
| author | Hugo Herbelin | 2018-05-25 18:33:26 +0200 |
|---|---|---|
| committer | Hugo Herbelin | 2018-09-27 22:36:30 +0200 |
| commit | bfbc82eb29c9dbf868d3decbd30b0462ea398ebd (patch) | |
| tree | 2ede0a652ac7e40b8734a4339fed19b88e3f3285 | |
| parent | b2361208a1242a92af7d18cb723ef3b7b55d79b5 (diff) | |
A word about PR #262 in CHANGES.
| -rw-r--r-- | CHANGES | 7 |
1 files changed, 6 insertions, 1 deletions
@@ -83,7 +83,7 @@ Focusing e.g. `[x]: {` will focus on a goal (existential variable) named `x`. As usual, unfocus with `}` once the sub-goal is fully solved. -Specification language +Specification language, type inference - A fix to unification (which was sensitive to the ascii name of variables) may occasionally change type inference in incompatible @@ -94,6 +94,11 @@ Specification language induce an overhead if the cost of checking the conversion of the corresponding definitions is additionally high (PR #8215). +- A few improvements in inference of the return clause of "match" can + exceptionally introduce incompatibilities (PR #262). This can be + solved by writing an explicit "return" clause, sometimes even simply + an explicit "return _" clause. + Standard Library - Added `Ascii.eqb` and `String.eqb` and the `=?` notation for them, |
