jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

alternative, much simpler algorithm for strict func checking (#21066)

Browse source 
* alternative, much simpler algorithm for strict func checking

* forgot to git add new compiler module

* new spec is incredibly simple to describe

* fixes bigints regression

* typos

* closes #16305; closes #17387; closes #20863
This commit is contained in:
Andreas Rumpf 2022-12-11 16:58:50 +01:00 • committed by GitHub
commit 3812d91390
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
14 changed files with 187 additions and 78 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/manual_experimental.md
View file

@ -519,8 +519,7 @@ Since version 1.4, a stricter definition of "side effect" is available.
In addition to the existing rule that a side effect is calling a function
with side effects, the following rule is also enforced:
Any mutation to an object does count as a side effect if that object is reachable
via a parameter that is not declared as a `var` parameter.
A store to the heap via a `ref` or `ptr` indirection is not allowed.
For example:
@ -540,17 +539,14 @@ For example:
it = it.ri
func mut(n: Node) =
let m = n # is the statement that connected the mutation to the parameter
m.data = "yeah" # the mutation is here
# Error: 'mut' can have side effects
# an object reachable from 'n' is potentially mutated
var it = n
while it != nil:
it.data = "yeah" # forbidden mutation
it = it.ri
```
The algorithm behind this analysis is described in
the [view types algorithm][Algorithm].
View types
==========