about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-11-17 18:53:15 +0000
committerbors <bors@rust-lang.org>2023-11-17 18:53:15 +0000
commite8e95102191dc0e2b718c8030103cfafd0869bf5 (patch)
tree77a1c201e3edbfe3678885dbfd47d47173d183e6 /tests/rustdoc-js-std/parser-errors.js
parent31e38fee23eb6a41047c18c2e99e4d6022d70d6f (diff)
parentaca4086d7f4c889d2e55908325c782706ef4fa4f (diff)
downloadrust-e8e95102191dc0e2b718c8030103cfafd0869bf5.tar.gz
rust-e8e95102191dc0e2b718c8030103cfafd0869bf5.zip
Auto merge of #11002 - y21:issue9422, r=Jarcho
teach `eager_or_lazy` about panicky arithmetic operations

Fixes #9422
Fixes #9814
Fixes #11793

It's a bit sad that we have to do this because arithmetic operations seemed to me like the prime example where a closure would not be necessary, but this has "side effects" (changes behavior when going from lazy to eager) as some of these panic on overflow/underflow if compiled with `-Coverflow-checks` (which is the default in debug mode).
Given the number of backlinks in the mentioned issues, this seems to be a FP that is worth fixing, probably.

changelog: [`unnecessary_lazy_evaluations`]: don't lint if closure has panicky arithmetic operations
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions