aboutsummaryrefslogtreecommitdiff
path: root/src/value.zig
diff options
context:
space:
mode:
authorIsaac Freund <mail@isaacfreund.com>2021-10-24 13:13:06 +0200
committerAndrew Kelley <andrew@ziglang.org>2021-10-24 15:04:29 -0400
commitf7b090d7076a20a614bf20cac05e5e18c06ad18a (patch)
tree72bb252c5352e48ea6d60914debdf5ccc1821dff /src/value.zig
parent6cf5305e47dd8382508f867b04067be615448b41 (diff)
downloadzig-f7b090d7076a20a614bf20cac05e5e18c06ad18a.tar.gz
zig-f7b090d7076a20a614bf20cac05e5e18c06ad18a.zip
std.log: simplify to 4 distinct log levels
Over the last year of using std.log in practice, it has become clear to me that having the current 8 distinct log levels does more harm than good. It is too subjective which level a given message should have which makes filtering based on log level weaker as not all messages will have been assigned the log level one might expect. Instead, more granular filtering should be achieved by leveraging the logging scope feature. Filtering based on a combination of scope and log level should be sufficiently powerful for all use-cases. Note that the self hosted compiler has already limited itself to 4 distinct log levels for many months and implemented granular filtering based on both log scope and level. This has worked very well in practice while working on the self hosted compiler.
Diffstat (limited to 'src/value.zig')
0 files changed, 0 insertions, 0 deletions