Correct result type#18
Merged
Merged
Conversation
added 6 commits
February 18, 2026 15:29
…ng an atomic bool. This is because we do not need pthread once: pthread once blocks other threads until the initialization is finished, but we do not need that, and atomics are faster than pthread once. A thread only needs to know if another thread won the race of resolving the promise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the result type: It has two states, not three (I had managed to somehow confuse it with the promise state, now both concepts are separate).
Also makes the async/await API thread-safe: