Closed
Bug 1607419
Opened 5 years ago
Closed 5 years ago
option.expect(&format!(...)) runs formatting code unconditionally
Categories
(Core :: Graphics: WebRender, defect, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: nical, Assigned: nical)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
And it slows some code down. The biggest offender is in BrushSegment::update_clip_task. which I caught while profiling (so surprising that I initially assumed fmt::format was showing in the profile because of some symbolication error).
The majority of the remaining expect(&format!
are in recording code so we don't need to worry about performance as much. Part of me itches to get rid of them as well just to prevent this knee-self-targeting pattern to look familiar.
Assignee | ||
Comment 1•5 years ago
|
||
Easy to miss that the slow formatting code is run unconditionally.
The remaining instances are in recording and startup code.
Comment 2•5 years ago
|
||
fwiw there's a clippy lint for this, and nical's fix is the suggested one: https://rust-lang.github.io/rust-clippy/master/index.html#expect_fun_call
Pushed by nsilva@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/031a2ee21fa6
Avoid option.expect(&format in hot code. r=jrmuizel
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•