# std.Progress: make the API thread-safe · gitcafe/zig

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

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

Visibility: public

Requested revision: aa6ef10cc657e2bbe59c362f27d7a557c43d7fae

Requested commit: aa6ef10cc657e2bbe59c362f27d7a557c43d7fae

Commit: aa6ef10cc657e2bbe59c362f27d7a557c43d7fae

Tree: d76bbb5d6912c53e3bad0cf8281459c24bbf3249

Author: Andrew Kelley

Committer: Andrew Kelley

## Message

```
std.Progress: make the API thread-safe

We generally get away with atomic primitives, however a lock is required
around the refresh function since it traverses the Node graph, and we
need to be sure no references to Nodes remain after end() is called.

```

## Parents

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

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