Sorry intention was not to start a tabs vs curly war again. Its to give a
flexibility and let the user opt for what they like. I feel more people will
give nim a try.
As far I understand, valgrind and address sanitizer uses large shadow memory
and in this case its not. This approach needs both compiler and library.
Benefit is probably existing code can work without any change and can be used
for any language like c/c++/d/nim. It may not be easy for a company
I do agree with what you say. Nim is flexible in lot of areas. My suggestion
was to give this flexibility here too so that people have option to use either
and may be more people join. Its worth to give a try.
`` I am not an expert on compilers and I might be completely stupid sharing an
approach for memory safety. I primarily code in c/c++. From what I understand
is both language and memory allocator should work together for memory safety.
My approach is that pointers store a handle(number) instead o
I feel lot of people will feel at home coming from c/c++/java/javascript. I do
understand there are benefits in both approaches. For anyone who is looking at
first at Nim, will think a better python but its actually much more than that.
It should feel a better go/c++ etc. I feel its worth the ef
A newbie, just a request and not a rant. Because Nim gave option to have case
insensitive so that different people can choose their own style. Will Nim do
the same for curly brace by adding curly brace too. So projects which like
curly, they can use that and projects which like tab can use that.