> Infinite recursion leading to a segfault is **a known bug with no plans to
> be fixed that I know of,** which I've encountered many times.
That's unfortunate; as I said in the bug report, it's so easy to trigger
and so easy to miss when reviewing the code! And the process crashing
instead of reporting an error is really a pity.
An explicit error message would be nice, but as I understand this would
require setting a hard limit on the call stack depth, which may bring other
On Thu, 30 Jan 2020 at 03:59, tyson andre <firstname.lastname@example.org> wrote: