Make CALL_STACK_LIMIT_EXCEEDED_ERR_MSG more generic

We're now using this when a stack overflow is detected during eval/substitution
loops, too.
This commit is contained in:
Mahmoud Al-Qudsi 2022-10-25 13:23:30 -05:00
parent 175caab583
commit 21599a49ea
2 changed files with 2 additions and 3 deletions

View File

@ -220,8 +220,7 @@ enum class pipeline_position_t : uint8_t {
/// Error message on reaching maximum call stack depth.
#define CALL_STACK_LIMIT_EXCEEDED_ERR_MSG \
_(L"The function call stack limit has been exceeded. Do you have an accidental infinite " \
L"loop?")
_(L"The call stack limit has been exceeded. Do you have an accidental infinite loop?")
/// Error message when encountering an unknown builtin name.
#define UNKNOWN_BUILTIN_ERR_MSG _(L"Unknown builtin '%ls'")

View File

@ -13,7 +13,7 @@ end
left
#CHECKERR: {{.*}} The function call stack limit has been exceeded. {{.*}}
#CHECKERR: {{.*}} The call stack limit has been exceeded. {{.*}}
#CHECKERR: {{.*}}
#CHECKERR: {{.*}}
#CHECKERR: {{.*}}