diff options
| author | Michael Goulet <michael@errs.io> | 2024-09-23 23:49:13 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-23 23:49:13 -0400 |
| commit | fa1bd9b06a643ea1e069d9d8a1f1b1b9ac559715 (patch) | |
| tree | bb9ae0431060fb58f6590a57bc047df5fe591aac /compiler/rustc_codegen_gcc | |
| parent | 4d0b44ab5b5ce21671ca64e15c22b299f2ed4985 (diff) | |
| parent | 9050b3374588fdb1b15a862a495b042dd64edd5a (diff) | |
| download | rust-fa1bd9b06a643ea1e069d9d8a1f1b1b9ac559715.tar.gz rust-fa1bd9b06a643ea1e069d9d8a1f1b1b9ac559715.zip | |
Rollup merge of #130758 - compiler-errors:ctype-recursion-limit, r=jieyouxu
Revert "Add recursion limit to FFI safety lint" It's not necessarily clear if warning when we hit the recursion limit is the right thing to do, first of all. **More importantly**, this PR was implemented incorrectly in the first place; it was not decrementing the recursion limit when stepping out of a type, so it would trigger when a ctype has more than RECURSION_LIMIT fields *anywhere* in the type's set of recursively reachable fields. Reverts #130598 Reopens #130310 Fixes #130757
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions