Closed andy-hanson closed 1 year ago
oh std.experimental.logger has changed it seems.
There was a StdLoggerDisableWarning
version in the dub.json, I guess it was to hide exactly these warnings?
This functionality seems to have been completely removed from std.logger now though (being able to toggle off individual logging levels)
However I think it makes more sense to print either only error messages or no messages from libdparse/dsymbol anyway. The actual application output that's supposed to be stable is done via stdout/stderr writeln anyway.
title should probably be changed since it's a library issue rather than a compiler one.
on my current project this logger spam alone completely blows out my terminal scrollback.
it's something that changed in phobos / std.experimental.logger - this is usually bundled with compiler versions
This reproduces with a simple project.
a.d:
b.d:
When I run
source ~/dlang/ldc-1.30.0/activate
thendub run dscanner -- --styleCheck *.d
, I get this (good) output (skipping build output):When I run
source ~/dlang/ldc-1.31.0-beta1/activate
thendub run dscanner -- --styleCheck *.d
, I get this (bad) output (skipping build output):On a larger project there will be a lot of "Could not resolve" errors, likely one for every import.