diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-23 19:53:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-23 19:53:41 +0200 |
| commit | ee08dd86582a15cf2755951f40c9e50adf72d39d (patch) | |
| tree | 4cfe9f8aa37f8d84e0e55e0ffcfde8c87e56f793 /tests/rustdoc-ui/coverage/enum-tuple.rs | |
| parent | 221039b416080319cd805ede73fc7968d33a5cbd (diff) | |
| parent | a4d6d9a24fddd74d8be54e454e17ed53a5d82514 (diff) | |
| download | rust-ee08dd86582a15cf2755951f40c9e50adf72d39d.tar.gz rust-ee08dd86582a15cf2755951f40c9e50adf72d39d.zip | |
Rollup merge of #111722 - mrcnski:stack-protector-doc, r=rcvalle
Document stack-protector option Only updated `exploit-mitigations.md` to reflect that the option exists. Removed the alternatives mentioned as they are not actually implemented yet. As this is an unstable feature, should it be added to `unstable-book` also? [Example](https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html). I didn't do that because I couldn't find the tracking issue for stack-protector. (There should be one to track stabilization of the feature, I think?) cc `@rcvalle`
Diffstat (limited to 'tests/rustdoc-ui/coverage/enum-tuple.rs')
0 files changed, 0 insertions, 0 deletions