Skip to content

Remove value setting from mutex locks - #16

Merged
vshalygin merged 1 commit into
mainfrom
issue_15
Sep 1, 2026
Merged

Remove value setting from mutex locks#16
vshalygin merged 1 commit into
mainfrom
issue_15

Conversation

@vshalygin

Copy link
Copy Markdown
Owner

Issue: Synchronously setting a future’s value while holding an external mutex can be dangerous because, in some cases, the future’s internal mutex and the external mutex may be acquired in the reverse order.

Solution: Set the future’s value only after releasing the external mutex.

Closes #15

@vshalygin vshalygin self-assigned this Sep 1, 2026
@vshalygin vshalygin added the bug Something isn't working label Sep 1, 2026
@vshalygin
vshalygin merged commit 6549551 into main Sep 1, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI failed

1 participant