refactor!(rs): make LoroDoc !Sync #687
Closed
+56
−23
Conversation
This file contains 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
Leeeon233
approved these changes
Mar 14, 2025
|
Close as it's not a perfect solution since LoroDoc is still Clone, which shares the underlying obj and can be then sent to another thread |
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.
Fix #685. It's a breaking change for the loro Rust crate.
LoroDoc should not be Sync because &LoroDoc is not safe to send to another thread. It may lead to misuse. !Sync + Send would require users to use Arc<Mutex> when they need to send LoroDoc to another thread.