Updated Common Criticisms (markdown)
This commit is contained in:
parent
0c8ccdf29f
commit
6fb534eb4a
|
@ -1,7 +1,7 @@
|
|||
## Nim doesn't require call-site annotation for `var` parameters
|
||||
This is referring to systems like C#'s: `void foo(ref int myInput){...}; foo(ref a);`. Note the ref on the `foo` call. If this was Nim, it'd be impossible to tell from the call-site that `foo` has the potential to modify `a`.
|
||||
|
||||
** * NOTE * ** : The following is wrong, I'll fix it soon
|
||||
***NOTE*** : The following is wrong, I'll fix it soon
|
||||
|
||||
Possibly. The problem here is that of perception. In many languages, heap allocation through pointers is the only method of having objects, and passing them to a function gives the freedom to modify them. In Nim, things can be allocated on the stack, and those things need to be treated in the same way as things on the heap.
|
||||
|
||||
|
|
Loading…
Reference in New Issue