diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-09-22 18:25:53 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-22 18:25:53 +0530 |
| commit | d5ae6737bfbe9d457d1a0984a7666568118e894b (patch) | |
| tree | b47501f06a722b1f03370cbabff32ad4b94e3206 /library/std/src/sys/unix/stack_overflow.rs | |
| parent | c99a603b87a4f333541d54ad119eaafe35ae9a61 (diff) | |
| parent | 1512ce5925eeafc01f011c46216c157e4e5644cb (diff) | |
| download | rust-d5ae6737bfbe9d457d1a0984a7666568118e894b.tar.gz rust-d5ae6737bfbe9d457d1a0984a7666568118e894b.zip | |
Rollup merge of #102037 - jyn514:normalize-docs, r=lcnr
Make cycle errors recoverable In particular, this allows rustdoc to recover from cycle errors when normalizing associated types for documentation. In the past, ```@jackh726``` has said we need to be careful about overflow errors: https://github.com/rust-lang/rust/pull/91430#issuecomment-983997013 > Off the top of my head, we definitely should be careful about treating overflow errors the same as "not implemented for some reason" errors. Otherwise, you could end up with behavior that is different depending on recursion depth. But, that might be context-dependent. But cycle errors should be safe to unconditionally report; they don't depend on the recursion depth, they will always be an error whenever they're encountered. Helps with https://github.com/rust-lang/rust/issues/81091. r? ```@lcnr``` cc ```@matthewjasper```
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions