-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Tracking Issue for timing report SVG render backend #16440
Copy link
Copy link
Closed
Labels
A-timingsArea: timingsArea: timingsC-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.S-waiting-on-feedbackStatus: An implemented feature is waiting on community feedback for bugs or design concerns.Status: An implemented feature is waiting on community feedback for bugs or design concerns.
Metadata
Metadata
Assignees
Labels
A-timingsArea: timingsArea: timingsC-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.S-waiting-on-feedbackStatus: An implemented feature is waiting on community feedback for bugs or design concerns.Status: An implemented feature is waiting on community feedback for bugs or design concerns.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
No status
See call for testing
Summary
Original issue: #8850
Implementation: #15091
This changes Cargo timing report renderer from HTML canvas to SVG, improving the performance of rendering large dependency graph, as well as hovering dependency lines.
Currently canvas is still the default, and there is a toggle switching between them during the call-for-testing period
Unresolved Issues
Future Extensions
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.