diff options
| author | metagn <metagngn@gmail.com> | 2024-10-03 21:39:55 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-03 20:39:55 +0200 |
| commit | 7dfadb8b4e95d09981fbeb01d85b12f23946c3e7 (patch) | |
| tree | be82d847e1a7dd4bebf1ca3605c97fa19d48c969 /tests/niminaction/Chapter7/Tweeter/src/views | |
| parent | 4eed341ba53e69674d7e8e8a609efd1ea0a54b4b (diff) | |
| download | Nim-7dfadb8b4e95d09981fbeb01d85b12f23946c3e7.tar.gz | |
stricter set type match, implicit conversion for literals (#24176) devel
fixes #18396, fixes #20142
Set types with base types matching less than a generic match (so
subrange matches, conversion matches, int conversion matches) are now
considered mismatching, as their representation is different on the
backends (except VM and JS), causing codegen issues. An exception is
granted for set literal types, which now implicitly convert each element
to the matched base type, so things like `s == {'a', 'b'}` are still
possible where `s` is `set[range['a'..'z']]`. Also every conversion
match in this case is unified under the normal "conversion" match, so a
literal doesn't match one set type better than the other, unless it's
equal.
However `{'a', 'b'} == s` or `{'a', 'b'} - s` etc is now not possible.
when it used to work in the VM. So this is somewhat breaking, and needs
a changelog entry.Diffstat (limited to 'tests/niminaction/Chapter7/Tweeter/src/views')
0 files changed, 0 insertions, 0 deletions