Compiler stack overflow with nested lambda functions

[pventuzelo]

Aim

We (https://github.com/FuzzingLabs) found that the compiler ends up overflowing its stack when you nest too many lambda functions.

Expected Behavior

No panic should occur.

Bug

In the given example, after 18 nested lambda functions, the compiler ends up overflowing its stack. 18 was the minimum needed to trigger the overflow with 64GB of RAM. Only lambda functions seem to have this issue. Things like for loops or function calls can be nested as much as desired.

The issue occurs with the latest compiler version on the master branch. The error message is as follows:

thread '<unknown>' has overflowed its stack
fatal runtime error: stack overflow
Abandon (core dumped)

To Reproduce

fn main() {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
let lambda = || {
};
};
};
};
};
};
};
};
};
};
};
};
};
};
};
};
};
};
}

Project Impact

None

Impact Context

No response

Workaround

None

Workaround Description

No response

Additional Context

The computer used has 64GB of RAM. This may impact how many lambda functions are needed to trigger the overflow of the stack.

Installation Method

None

Nargo Version

No response

NoirJS Version

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response

[TomAFrench]

This compiles on the new parser #6180 so I'm going to close this issue.