fix: reject inexact integer literals in float context

This commit is contained in:
2026-10-24 01:02:20 +02:00
parent 9c1bd2a20e
commit 5fd8d9eb89
5 changed files with 58 additions and 4 deletions
-3
View File
@@ -1,3 +0,0 @@
- [ ] consider whether numeric conversion semantics are properly tuned.
- e.g. are we disallowing implicit conversion between types where loss of precission or wrapping could/would occur?
- should we do that or should we not?