diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-12-01 04:49:24 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-01 04:49:24 +0100 |
| commit | 60f4212ee537c7f5efff51c694c814b5458c8aa7 (patch) | |
| tree | 0aa7ab4c9c6360843bb8efe44bb1dc46376ac82e /src/liballoc/alloc | |
| parent | 99f9fa36951b25eba43e822bd5a58508d5f22d28 (diff) | |
| parent | 52426ab42dffadfcaec7d1eb4afa4d63cca11593 (diff) | |
| download | rust-60f4212ee537c7f5efff51c694c814b5458c8aa7.tar.gz rust-60f4212ee537c7f5efff51c694c814b5458c8aa7.zip | |
Rollup merge of #66726 - CAD97:miri-recursion-limit, r=RalfJung
Use recursion_limit for const eval stack limit
cc https://github.com/rust-lang/miri/issues/643 @orium @RalfJung
I'm really not certain how exactly to handle this change, but it looks like it's that simple.
Reuse `recursion_limit` ("The maximum recursion limit for potentially infinitely recursive operations such as auto-dereference and monomorphization") which is configurable by the user for the const evaluation stack frame limit.
The other option is to make `const_eval_stack_frame_limit` configurable in the same way as `recursion_limit` (but I'm not sure how to do that and it'd be a bigger change).
Fixes https://github.com/rust-lang/miri/issues/643.
Diffstat (limited to 'src/liballoc/alloc')
0 files changed, 0 insertions, 0 deletions