diff options
| author | bors <bors@rust-lang.org> | 2020-04-08 13:14:50 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-04-08 13:14:50 +0000 |
| commit | 0b4098335d9ea2468f0ceea82f3c8315fa5decc1 (patch) | |
| tree | 666b5c8fdd040e963f4ac9bc753d1dea6bcf4ef5 /src/rustllvm/CoverageMappingWrapper.cpp | |
| parent | d342cee78703c46d9df09088f9fb99ba85d021ae (diff) | |
| parent | 1647f53fb3064e7bf86d396b401bca0f90a9d51d (diff) | |
| download | rust-0b4098335d9ea2468f0ceea82f3c8315fa5decc1.tar.gz rust-0b4098335d9ea2468f0ceea82f3c8315fa5decc1.zip | |
Auto merge of #5429 - faern:use-assoc-int-float-consts, r=flip1995
Use assoc int and float consts instead of module level ones
changelog: Recommend primitive type associated constants instead of module level constants
In Rust 1.43 integer and float primitive types will have a number of new associated constants. For example `MAX`, `MIN` and a number of constants related to the machine representation of floats. https://github.com/rust-lang/rust/pull/68952
These new constants are preferred over the module level constants in `{core,std}::{f*, u*, i*}`. I have in the last few days made sure that the documentation in the main rust repository uses the new constants in every place I could find (https://github.com/rust-lang/rust/pull/69860, https://github.com/rust-lang/rust/pull/70782). So the next step is naturally to make the linter recommend the new constants as well.
This PR only changes two lints. There are more. But I did not want the PR to be too big. And since I have not contributed to clippy before it felt saner to start with a small PR so I see if there are any quirks. More will come later.
Diffstat (limited to 'src/rustllvm/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions