You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the introduction of the standardized Log framework (#8847 and others), it has only received limited application in stdlib.
There are currently 23 calls to a log method outside src/log, half of them in the compiler's playground server (which used the old Logger class before), the rest is in HTTP::Server and OpenSSL.
For the size of the standard library this amount of logging coverage is is way to little. Especially considering what a powerful and flexible tool Log is.
So I'm wondering what's the best way to improve this. Just go through entire stdlib file by file and see what could use some logging? Or better a prioritized approach focusing on most relevant features?
The text was updated successfully, but these errors were encountered:
Since the introduction of the standardized
Log
framework (#8847 and others), it has only received limited application in stdlib.There are currently 23 calls to a log method outside
src/log
, half of them in the compiler's playground server (which used the oldLogger
class before), the rest is inHTTP::Server
andOpenSSL
.For the size of the standard library this amount of logging coverage is is way to little. Especially considering what a powerful and flexible tool
Log
is.So I'm wondering what's the best way to improve this. Just go through entire stdlib file by file and see what could use some logging? Or better a prioritized approach focusing on most relevant features?
The text was updated successfully, but these errors were encountered: