`#maybe try this: import threadpool var messageFlowVar = spawn stdin.readLine()
stdout.write "> " var s = ^messageFlowVar echo "you wrote: ", s `
Run
In what sense is `owned` "a wrapper"? And why does that cause problems with
"nesting"?
You are now in crazy-talk-land... "deepDestroy"? destroying 'ptr'
automatically? What's wrong with B/D anyway? Please read their paper again,
their design does not mention any of this crazy stuff. They wrote
@Araq, regarding my thinking on the treatment of raw pointers to do with
"owned":
> The only complication on automatic application of the "simple rule" is what
> to do with the raw pointers pointer and ptr T which might reference the heap
> but can reference any memory location anywhere includi
I'm sad to see strongSpaces go. (hey I still kinda prefer the old case
insensitivity back when Nim was still Nimrod).
Are there plans to have a bunch of awesome examples and PR material prepared
once we hit 1.0?
Please consider including the topics discussed in the title of the video
instead of just writing "Nim Development Blog ".
thank you! issue added!
contents:
after upgrading to 0.20.0 my app not compiles:
Hint: 378820 [Processing]
/Users/travis/build/nim-lang/nightlies/nim/e7471cebae2a404f3e4239f199f5a0c422484aac/lib/system/fatal.nim(48)
sysFatal|
---|---
Error: unhandled exception: value out of range: -1 [
Second video has arrived:
[https://youtu.be/8qdagbtgl-8](https://youtu.be/8qdagbtgl-8)
This doesn't work when I have to do: `messageFlowVar = spawn stdin.readLine()`
I also tried: `messageFlowVar = spawn readLineFromStdin "> "`
any idea?
Sorry, I’m French and for me positive means strictly positive (as negative
means strictly negative), but to avoid any ambiguity, I always use «
strictement positif » for numbers > 0 and « positif ou nul » for numbers ≥ 0.
Some authors (Bourbaki for instance) considers that zero is both a positiv
