-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed as not planned
Labels
C-featureCategory: feature requestCategory: feature request
Description
When writing high performance code, it becomes vitally important to know if loop bounds checking has been optimized out, or if arithmetic underflow/overflow checks have been proven to not be possible, for example. The way I do this currently is to copy-paste bits of code into godbolt, or to manually scan .d files in target. Is it within scope of rust-analyzer to track this kind of information and present it so that it can be highlighted in the IDE? There is probably a nicer way to test for the panic handlers being dead-code eliminated within the rust compilation, than to look at the final assembly.
Metadata
Metadata
Assignees
Labels
C-featureCategory: feature requestCategory: feature request