fixes #10038; deprecate generic methods, they are unreliable
This commit is contained in:
parent
36a398d96f
commit
16aa10dfe1
3 changed files with 8 additions and 3 deletions
|
|
@ -33,6 +33,7 @@
|
|||
tree from the symbol declaration instead of just the initializer portion.
|
||||
|
||||
- To use multi-methods, explicit `--multimethods:on` is now needed.
|
||||
- Generic methods are now deprecated; they never worked well.
|
||||
|
||||
- Compile time checks for integer and float conversions are now stricter.
|
||||
For example, `const x = uint32(-1)` now gives a compile time error instead
|
||||
|
|
@ -45,7 +46,8 @@
|
|||
- A bug allowed `macro foo(): int = 123` to compile even though a
|
||||
macros has to return a `NimNode`. This has been fixed.
|
||||
|
||||
- With the exception of `uint` and `uint64`, conversion to unsigned types are now range checked during runtime.
|
||||
- With the exception of `uint` and `uint64`, conversion to unsigned types
|
||||
are now range checked during runtime.
|
||||
|
||||
#### Breaking changes in the standard library
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue