Hey! I was curious about the reasons behind the guard clause limitations. Am I correct in guessing that it’s a limitation/optimization in BEAM that prevents function calls in there? If so, are there patterns/operations that would be possible in the VM that Gleam will hopefully enable in the future, or is the current set of operations all there will be, unless the BEAM itself enables more?
#Guard clause limitations
1 messages · Page 1 of 1 (latest)