Move heaplang.sty towards being a community standard
Similarly to #488 I believe it is beneficial to more carefully curate the heaplang.sty
file contained in this repository.
Some immediate considerations that might make sense to review are:
- The notion-style supported by the language macros - e.g. parentheses vs spaces for function arguments
- The naming of each macro, to avoid clashes with popular latex packages
- Discuss what similarities we want HeapLang to have with existing languages (formerly ML, but has since moved quite past it)
- Casing of constructs, both in Latex and notation. Currently we have discrepancies such as
ref
andAlloc
even though they live on the same level. The latex macros are mostly consistent, with some outliers like\poison
and\fold
/\unfold
The MR's !852 (merged) and !853 (merged) are some initial steps in this direction.