| 7 | | Constant Applicative Forms, or CAFs for short, are top-level values defined in a program. |
| 8 | | To avoid memory leaks caused by CAFs we need to detect when all values/functions that could potentially refer to a CAF are gone, and so it is safe to deallocate the CAF. |
| | 7 | Constant Applicative Forms, or CAFs for short, are top-level values defined in a program. |
| | 8 | Essentially, they are objects that are not allocated dynamically at run-time but, instead, |
| | 9 | are part of the static data of the program. Sometimes, a CAF may refer to many values in the heap. This is why, we need to know when a CAF is never going to be used again by the program, and |
| | 10 | hence the values to which it refers may be garbage collected. |
