Provide more information about call stack in case of stack overflow during compilation #64929
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Compiling code with custom macros
results in
That's full message with no information about place in code which caused a problem and with no call stack even if
RUST_BACKTRACE=full
set.It would be better if compiler could handle this type of exceptions and provide some debug information (call stack at least).
The text was updated successfully, but these errors were encountered: