There were several warnings I saw, including some related to cstrings, at
various points compiling using Nim built from Nim devel git, but at more recent
points in Nim development when I've tried this, the warnings had disappeared,
so it might be worth checking how things go after that version i
Even if it's not unsafe, it could affect performance to convert Nim strings to
JS strings, and it's better if this is explicitly shown.
In general to prevent too many cstring conversions, you can try to work
directly on cstring. Sometimes you may need to `importjs` some JS string
methods to mak
well, it's handled in sempass2, maybe we should disable this warning for js
target ？
I'm updating some little hobby project that uses the Javascript backend and I'm
noticing some new warnings:
> Warning: implicit conversion to 'cstring' from a non-const location: ...;
> this will become a compile time error in the future
(I'm using Nim 1.6.8 and this warning may have been intro
