|1.1.0||Jun 23, 2023|
|1.0.0||Nov 18, 2020|
#129 in Programming languages
42,049 downloads per month
Used in 19 crates (4 directly)
Force Send Sync
Tells the compiler things are Send and/or Sync.
Reasons not to use this crate
If you should not know what
Sync means this crate is likely not what you are looking
for. Usecases for this are extremly rare. This crate is unlikely to solve your problem and much more
likely to turn the problem you have into a much messier one.
Reasons to use this crate
- You have a type which
Syncbut the compiler does not know it. Further you can not implement these yourself, because the code lives Upstream (maybe you could contribute there?).
- You have a really weird situation there safety of these depends on configuration read at runtime and you need a way to promote safety of types.
Please do not use this crate. The Rust compiler tries to protect you for a reason. Do under no
circumstances use this to silence some compiler error you do not understand. Only use this if
you do understand why your type is
Send and or
Sync, and also understand why the compiler
disagrees with you.