-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix recursion limits #57074
Fix recursion limits #57074
Conversation
What's the motivation/reason for this change? Looks to me like it already works fine. Or is this solely exposed on parallel queries? If so, how does that happen? Is it the ordering changes, so just some queries that don't recurse so deep normally because some level down they already got cached? |
This is for parallel queries. We run into the default recursion limit when finding out if the AST is |
@bors r+ rollup |
📌 Commit 0c4d551 has been approved by |
Fix recursion limits r? @michaelwoerister
Rollup of 10 pull requests Successful merges: - #55470 (box: Add documentation for `From` impls) - #56242 (Add missing link in docs) - #56944 (bootstrap: Link LLVM as a dylib with ThinLTO) - #56978 (Add `std::os::fortanix_sgx` module) - #56985 (Allow testing pointers for inboundedness while forbidding dangling pointers) - #56986 (rustc: Move jemalloc from rustc_driver to rustc) - #57010 (Actually run compiletest tests on CI) - #57021 (Enable emission of alignment attrs for pointer params) - #57074 (Fix recursion limits) - #57085 (librustc_codegen_llvm: Don't eliminate empty structs in C ABI on linux-sparc64) Failed merges: r? @ghost
r? @michaelwoerister