Add a recursion limit for the interpreter's expression runner (#2160)

We previously had one for calls (the spec tests check for infinite recursion).

This is an internal limit of the interpreter, until we un-recursify it, which may make sense at some point - but it's unlikely interpreting massively-recursive things will be beneficial in the optimizer anyhow, since if it could do something with them, it could also do so on the smaller pieces iteratively.

0 files changed, 0 insertions, 0 deletions