Do not attribute G-machine to SPJ specifically
All checks were successful
continuous-integration/drone/push Build is passing

This commit is contained in:
Danila Fedorin 2020-02-23 21:29:21 -08:00
parent f7a7100fea
commit eac1151616

View File

@ -128,7 +128,7 @@ there's another way.
We clean up after ourselves. We clean up after ourselves.
### Towards a Cleaner Stack ### Towards a Cleaner Stack
Simon Peyton Jones wrote his G-machine semantics in a particular way. Every time The G-machine compilation rules Simon Peyton Jones presents are written in a particular way. Every time
that a function is called, all it leaves behind on the stack is the graph node that a function is called, all it leaves behind on the stack is the graph node
that represents the function's output. Our own internal functions, however, have been less that represents the function's output. Our own internal functions, however, have been less
careful. Consider, for instance, the "binary operator" function I showed you. careful. Consider, for instance, the "binary operator" function I showed you.