Skip to content
This repository has been archived by the owner on Jan 2, 2021. It is now read-only.

Better progress messages #379

Merged
merged 3 commits into from
Feb 3, 2020
Merged

Conversation

ndmitchell
Copy link
Collaborator

Instead of saying how many nodes are in the Shake graph, we instead say how many files have started in the Shake graph. Unlike the previous measure, it isn't guaranteed to be monotonically increasing, as you might start additional rules after running files. But, in practice it seems pretty good, as we're hooking in somewhere very low level, the numbers "have the right feel" - when I have a project open the number roughly corresponds to the number of files, and roughly feels like the work is checking files. It also has more overhead, but if that's a problem, could be redone in terms of IORef to avoid the Var.

Probably worth someone other than me also playing with it to confirm it "feels right".

Fixes #320

@ndmitchell ndmitchell changed the title Better progress Better progress messages Jan 27, 2020
Copy link
Collaborator

@cocreature cocreature left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks very reasonable, thank you!

@cocreature cocreature merged commit f3abff8 into haskell:master Feb 3, 2020
pepeiborra pushed a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
* Require shake-0.18.4 which contains actionBracket

* Change progress reporting to use files rather than Shake nodes

* Remove inadvertantly writing down Shake twice
pepeiborra pushed a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
* Require shake-0.18.4 which contains actionBracket

* Change progress reporting to use files rather than Shake nodes

* Remove inadvertantly writing down Shake twice
pepeiborra pushed a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
* Require shake-0.18.4 which contains actionBracket

* Change progress reporting to use files rather than Shake nodes

* Remove inadvertantly writing down Shake twice
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Processing message should be in terms of files
2 participants