string to cstring conversions produce the empty C string for nil; this will be consistent with alternative string implementations
This commit is contained in:
parent
84c4e7a502
commit
aded62520b
3 changed files with 9 additions and 6 deletions
|
|
@ -11,7 +11,7 @@
|
|||
to deal with!
|
||||
- Indexing into a ``cstring`` for the JS target is now mapped
|
||||
to ``charCodeAt``.
|
||||
- Assignments that would "slice" an object into its supertype are not prevented
|
||||
- Assignments that would "slice" an object into its supertype are now prevented
|
||||
at runtime. Use ``ref object`` with inheritance rather than ``object`` with
|
||||
inheritance to prevent this issue.
|
||||
|
||||
|
|
@ -81,6 +81,9 @@
|
|||
Imported exceptions can be raised and caught just like Nim exceptions.
|
||||
More details in language manual.
|
||||
|
||||
- ``nil`` for strings/seqs is finally gone. Instead the default value for
|
||||
these is ``"" / @[]``.
|
||||
|
||||
### Tool changes
|
||||
|
||||
- ``jsondoc2`` has been renamed ``jsondoc``, similar to how ``doc2`` was renamed
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue