-
Notifications
You must be signed in to change notification settings - Fork 733
chore: inline trace nodes #11954
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
chore: inline trace nodes #11954
Conversation
|
!bench |
|
Benchmark results for 5b9e69e against e766839 are in! @Kha @eric-wieser Runs (2🟥)
|
5b9e69e to
663d1e7
Compare
|
!bench |
|
Benchmark results for 663d1e7 against e766839 are in! @Kha Large changes (4🟥)
Medium changes (6✅, 22🟥)Too many entries to display here. View the full report on radar instead. Small changes (211✅, 32🟥)Too many entries to display here. View the full report on radar instead. |
|
Mathlib CI status (docs):
|
|
Reference manual CI status:
|
|
!bench mathlib |
|
Benchmark results for leanprover-community/mathlib4-nightly-testing@0022380 against leanprover-community/mathlib4-nightly-testing@7c43efe are in! @Kha No significant changes detected. |
This extracts a `postCallback` helper so that only the actual callback is inlined.
663d1e7 to
0bfb4b6
Compare
This extracts a
postCallbackhelper so that only the actual callback is inlined.Part of the motivation here is to exclude these tracing frames from flame graph profiles.