-
Updated
Nov 3, 2020 - Go
diagnostics
Here are 247 public repositories matching this topic...
-
Updated
Nov 13, 2020 - C#
-
Updated
Nov 3, 2020 - SCSS
-
Updated
Aug 27, 2020 - C#
-
Updated
Nov 26, 2020 - Java
-
Updated
Sep 20, 2020 - Go
-
Updated
Dec 2, 2020 - Rust
-
Updated
May 9, 2017 - C
-
Updated
Sep 3, 2020 - Go
-
Updated
Sep 8, 2017
-
Updated
Jan 30, 2020 - PHP
-
Updated
Sep 28, 2017 - JavaScript
-
Updated
Nov 20, 2020 - Swift
-
Updated
Sep 29, 2020 - C#
-
Updated
Oct 29, 2016 - C
-
Updated
Mar 14, 2018 - Go
-
Updated
Dec 1, 2020 - C#
-
Updated
Feb 6, 2016 - PowerShell
-
Updated
Jul 5, 2020 - TypeScript
-
Updated
Mar 21, 2019 - PowerShell
-
Updated
Nov 3, 2020 - JavaScript
-
Updated
Nov 13, 2019 - C#
-
Updated
Dec 3, 2018 - JavaScript
-
Updated
Dec 22, 2019 - C#
-
Updated
Jul 21, 2020 - R
-
Updated
Nov 15, 2020 - Go
-
Updated
Jan 3, 2019
Improve this page
Add a description, image, and links to the diagnostics topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the diagnostics topic, visit your repo's landing page and select "manage topics."
Feature Request
Crates
tracing::instrumentMotivation
The
tracing::instrumentproc macro is incredibly useful, and the docs encourage users to use it, as well as set a level. Not all users read documentation, so many use defaults. (Like me)By default, they seem to decorate at all logging levels, which can impact performance for users in unexpected ways.
We met thi