Skip to content

chore: forward port 1.38.x#7239

Merged
carllerche merged 6 commits intotokio-1.43.xfrom
forward-port-1.38.x
Apr 4, 2025
Merged

chore: forward port 1.38.x#7239
carllerche merged 6 commits intotokio-1.43.xfrom
forward-port-1.38.x

Conversation

@carllerche
Copy link
Copy Markdown
Member

Forward ports #7232 to 1.43.x

Darksonn and others added 5 commits July 22, 2024 23:22
The broadcast channel does not require values to implement `Sync` yet it calls
the `.clone()` method without synchronizing. This is unsound logic. This patch
adds per-value synchronization on receive to handle this case. It is unlikely
any usage of the broadcast channel is currently at risk of the unsoundeness
issue as it requires accessing a `!Sync` type during `.clone()`, which would be
very unusual when using the broadcast channel.
@carllerche carllerche changed the base branch from master to tokio-1.43.x April 4, 2025 15:20
@github-actions github-actions Bot added the R-loom-sync Run loom sync tests on this PR label Apr 4, 2025
@carllerche carllerche force-pushed the forward-port-1.38.x branch from 95f4029 to a7b658c Compare April 4, 2025 15:31
@carllerche carllerche merged commit a7b658c into tokio-1.43.x Apr 4, 2025
82 checks passed
@carllerche carllerche deleted the forward-port-1.38.x branch April 4, 2025 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R-loom-sync Run loom sync tests on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants