# Sema: fix unreasonable progress node numbers · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/5f7a0bbabfde4eeb0ff4f40f0942ef710b6104a1)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 5f7a0bbabfde4eeb0ff4f40f0942ef710b6104a1

Requested commit: 5f7a0bbabfde4eeb0ff4f40f0942ef710b6104a1

Commit: 5f7a0bbabfde4eeb0ff4f40f0942ef710b6104a1

Tree: 33d506f40e4f7eef8b423ba1740c77675a0c5428

Author: mlugg

Committer: Matthew Lugg

## Message

```
Sema: fix unreasonable progress node numbers

The "completed" count in the "Semantic Analysis" progress node had
regressed since 0.14.0: the number got crazy big very fast, even on
simple cases. For instance, an empty `pub fn main` got to ~59,000 where
on 0.14 it only reached ~4,000. This was happening because I was
unintentionally introducing a node every time type resolution was
*requested*, even if (as is usually the case) it turned out to already
be done. The fix is simply to start the progress node a little later,
once we know we are actually doing semantic analysis. This brings the
number for that empty test case down to ~5,000, which makes perfect
sense. It won't exactly match 0.14, because the standard library has
changed, and also because the compiler's progress output does have some
*intentional* changes.

```

## Parents

- [2a8751e37f1e4d978400a95faca05119f17cf598](https://git.cafe/gitcafe/zig/commit/2a8751e37f1e4d978400a95faca05119f17cf598?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/5f7a0bbabfde4eeb0ff4f40f0942ef710b6104a1?format=markdown)