Don't lint numeric overflows in promoteds in release mode#50841
Don't lint numeric overflows in promoteds in release mode#50841bors merged 3 commits intorust-lang:masterfrom
Conversation
|
cc @nikomatsakis I don't think this is a complete solution, but is it even on the right path? |
|
Repeating my statement from IRC: This might leak memory/not run destructors. I don't see the issue with that, because to reach this code, you have to ignore a lint (soon to be deny-by-default) in order to get here. Yes this might be happening in a dependency, but right now you can only reach this by either doing UB (or at least very shady unsafe stuff) inside a constant or comparing addresses of constant values inside a constant. |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
7f235b4 to
5b45767
Compare
|
Ok... so the errors that are happening here make it seem to me like this is not the way to go. This would become a very messy codegen_llvm solution. I just left in the regression part |
|
@bors r+ |
|
📌 Commit 2ec0421 has been approved by |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
778b5f1 to
304ab16
Compare
|
@bors r=eddyb just a test that needed adjusting |
|
📌 Commit 304ab16 has been approved by |
|
☔ The latest upstream changes (presumably #50653) made this pull request unmergeable. Please resolve the merge conflicts. |
304ab16 to
8753d0f
Compare
|
@bors r=eddyb |
|
📌 Commit 8753d0f has been approved by |
|
☀️ Test successful - status-appveyor, status-travis |
r? @eddyb
mitigates #50814