diff options
| author | kennytm <kennytm@gmail.com> | 2018-04-04 11:07:10 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-04-04 11:07:10 +0200 |
| commit | b7b2ae2b6f88ea29290e0b25576c4a92690c0e26 (patch) | |
| tree | f0b86b0d4b20c17cc0a29484d6b6d271357c4acb /src/rustllvm/RustWrapper.cpp | |
| parent | 5758c2dd14fd29caf7c7bb2123eb6b23443b9233 (diff) | |
| parent | b2ed9dd546e33ded4a80acd02e1710fe811936b2 (diff) | |
| download | rust-b7b2ae2b6f88ea29290e0b25576c4a92690c0e26.tar.gz rust-b7b2ae2b6f88ea29290e0b25576c4a92690c0e26.zip | |
Rollup merge of #49179 - varkor:future-deprecation, r=QuietMisdreavus,GuillaumeGomez
Handle future deprecation annotations This adds special handling to the `since` parameter of the `deprecated` attribute: in particular, if the `since` version exceeds the version of the compiler, the deprecation notice will not be printed; but a note is added to the documentation stating that the item will be deprecated in a later version. (I've used `since` for this, rather than adding a new attribute, because it's more seamless and, I feel, intuitive. Plus it involves less code churn.)   This is a prerequisite for doing things renaming methods in the standard library (e.g. #30459). Resolves #30785.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions