How would the tester know which tests are failing without running all tests?
How do you use the memTracker compiler option to track memory usage?
What I tried was:
* added --memTracker:on to the compile line
* added line to my main module to import nimtracker
When I run my program, the memtracker.db file gets created and sqlite3 can view
it. However the tracker
That's what I would assume, but I wasn't sure if there was an underlying
omitted feature or something else going on
Have you considered looking in the Nim Api docs?
[https://nim-lang.github.io/Nim/unicode.html#runeLenAt%2Cstring%2CNatural](https://nim-lang.github.io/Nim/unicode.html#runeLenAt%2Cstring%2CNatural)
Is there an easy way to determine how many bytes a rune uses?
So a revised "Things I Recommend" list:
* Checking that Nimble metadata matches the package.
* Have `nimble init` suggest "Apache || MIT" as an option above plain
"Apache". ("License nagging" in favor of this is becoming very common in the
Rust community, which would totally destroy Nim's
About `mut` or `var` syntax.
1\. For `T` is value type, `var x: T` or `x: var T`, here `x=y` or `x.p=y`
means change the `value` of `x`, so variable `x` is same as the `value`.
2\. For `T` is ref type, `var x: T` or `x: var T`, here `x` is the pointer to
the `value`, `x=y` means change the
`Immutability` just like `static type`, `noSideEffect`, it is very useful
feature to write reliable correct code, and we have no other way to make the
ref type immutable.
Isn't it a bug that should be reported though? Overload resolution should
prefer more specified over less specified version, shouldn't it?
Ok, I consider this case closed. Nim lacks deep immutability because it's hard.
:-)
Indeed I was wondering about a similar problem myself some time ago, but not
really serious...
Well, you have defined a generic data type, so the generic proc version is
used. My first idea was to move the nongeneric proc above the generic one, in
the hope that compiler would pick the first
11 matches
Mail list logo
