Andreas Rumpf
This talk explains Nim’s move semantics and their connection to reference counting, how Nim’s model differs from C++ and why move semantics can offer superior performance. Nim with deterministic memory management never has been easier.
Move semantics for Nim
Nim is such a compelling language to use, I hope it can continue to grow and be used. It has this feeling of being such a pure language. Down in the metal, but not burdened with a terrible syntax like Rust.
On that question about nilability and you answered that Nim style moves can't use a variable after it is used and so the compiler can pretend that it's ok to set it to nil even when it is non-nilable. I think it a better solution is to have destructive moves where it doesn't call the destructor and lets the moved from variable just fall off the stack.
I am still wondering cuda with nim. There is nimcuda but it is only supports cuda 8. Cuda is very important to grow nim at hpc area.
I am using Python because modules and good gpu support.
programing in nim is pure joy, i am beginner though