-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Add tracing span macro calls to the language server for better debugging #6238
Conversation
Benchmark for a2ed695Click to view benchmark
|
8544b08
to
9215b58
Compare
Benchmark for 77cb7d5Click to view benchmark
|
ef28f0d
to
4461ad3
Compare
Benchmark for 0ab0fc9Click to view benchmark
|
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.
Generally we seem to be trying to catch function spans. I think #[instrument]
will already do that and might be cleaner if you prefer it: https://docs.rs/tracing/latest/tracing/attr.instrument.html, otherwise happy to approve
Yeah nice, can see how this would be handy in certain situations. I'll probably prefer to stick with this current approach for now though. Thanks for sharing though! |
Benchmark for 206b2adClick to view benchmark
|
Benchmark for 5bbf20aClick to view benchmark
|
Benchmark for e828064Click to view benchmark
|
…ing (#6238) ## Description closes #6220 ## Checklist - [x] I have linked to any relevant issues. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [x] If my change requires substantial documentation changes, I have [requested support from the DevRel team](https://github.com/FuelLabs/devrel-requests/issues/new/choose) - [x] I have added tests that prove my fix is effective or that my feature works. - [x] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [x] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [x] I have requested a review from the relevant team or maintainers.
Description
closes #6220
Checklist
Breaking*
orNew Feature
labels where relevant.