-
-
Notifications
You must be signed in to change notification settings - Fork 388
Trace rebuilds #2283
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
Trace rebuilds #2283
Conversation
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.
lgtm, thanks
3ab6ebb
to
cb4c256
Compare
cb4c256
to
f342001
Compare
ghcide/src/Development/IDE/Main.hs
Outdated
@@ -239,8 +239,8 @@ stderrLogger logLevel = do | |||
telemetryLogger :: IO Logger | |||
telemetryLogger | |||
| userTracingEnabled = return $ Logger $ \p m -> |
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.
withEventTrace
also contains this guard. You could remove it; but that would change this from a single check of userTracingEnabled
to create a no-op Logger
to a check of userTracingEnabled
on every step. Not sure if that's bad, but probably worth a comment to make it clear it's a deliberate decision if so.
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.
good shout, I'll add a comment
as pointed out by @michaelpj the check is already installed in withTracing the logger should not make any assumptions regarding user tracing being static anyway
Add more tracing to investigate module rebuilds and key dirtiness