I never thought anything was inconsistent about `newSeq` and `newString`.
Strings and sequences are value types, but they are still GC'd.
* * *
Oh, and the other thing to note is that we're working on the new runtime, where
strings and sequences can be non-GC. This brings both types closer in
A 64-bit Linux distro I run in VirtualBox updated from clang 3.9 to 6.0, so I
recompiled some code to compare the differences. The code compiled with
`--cc:clang` on 3.9, but using 6.0 it gives the following error output.
Hint: [Link]
/usr/bin/ld: cannot find crtbegin.o: No
> There should be an error for exported procs that take private types as
> parameters or return types IMO.
Agreed, that's what put me in a head scratching moment.
> I also advise you don't use this library in normal code as the person who
> wrote it is fairly new to Nim
Ah, well, so am I,
> Is this possible currently? Where can I find more information about how the
> garbage collector works. I saw that for real time garbage collection, the
> function that allows you to specify the maximum time the garbage collector
> can collect for determines the time that has passed using OS
Making `nim program.nim` functional goes against the purpose of this thread.
Unneeded stuff should be removed, not added.
There should be an error for exported procs that take private types as
parameters or return types IMO.
I like the idea of making nim program.nim functional. I don't know if it should
run or not (maybe 50% of the times?).
Congratulations !
I especially like the neural network examples and hope more
will be forthcoming.
Hello,
I should probably re-read Dominik's book but before I'll do that, can you help
me with one problem. I'm still confused (as in "I forget" not "I don't
understand") about module importing. Yesterday I was trying to hack a little
toy I wanted to configure with ini files. I found
@sherjilozair
That are very subjective recommendations, with some disadvantages.
"nim program" as a default alias for "nim c -r program.nim" with hidden
executable would mean that program is compiled again and again for each
execution -- until user discovers that he can just execute the
This is not so much about removing features, but about making nim friendly for
beginner programmers, or programmers who work at a higher abstraction layer
(Python users). In my opinion, the fact that nim actually compiles to C code,
and then compiles to binaries, and then runs the binaries
11 matches
Mail list logo
