-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[WIP] Everybody gets a tracer #15665
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
Conversation
6c011ad
to
d24402d
Compare
d24402d
to
365effe
Compare
6372944
to
9896b1b
Compare
@swift-ci please test |
Build failed |
Build failed |
9896b1b
to
d4022e3
Compare
d4022e3
to
388e357
Compare
@swift-ci please test |
1 similar comment
@swift-ci please test |
Build failed |
Build failed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fantastic! The only comment I have is to please update docs/RequestEvaluator.md
to remove the entry that asks someone to implement this.
@swift-ci please test and merge |
1 similar comment
@swift-ci please test and merge |
This PR has been dragging on for .. a while .. but I think it's probably worth merging now. The punchline is that every request (in the request-evaluator sense) now gets traced/profiled automatically, and a fair quantity of their arguments do too. I also sprinkled a few others around places I thought might be interesting, expanded the entity vocabulary, and improved the formatting of entity names where possible. The trace logs and profiles are roughly readable/informative now.
(I tried to do quite a lot of template-metaprogram tricks to cut down on the number of explicit overloads and specializations relative to the vocabulary here, all of them either failed in some resolution-ordering corner case I couldn't figure out, or else broke the layering-violation-avoidance tricks, so wouldn't link. I'm happy enough with this state.)