#sync #send #force


Unsafe wrappers to force Send and Sync

2 stable releases

1.1.0 Jun 23, 2023
1.0.0 Nov 18, 2020

#129 in Programming languages

Download history 5195/week @ 2023-08-02 5393/week @ 2023-08-09 5739/week @ 2023-08-16 5732/week @ 2023-08-23 4481/week @ 2023-08-30 4804/week @ 2023-09-06 7006/week @ 2023-09-13 6926/week @ 2023-09-20 7794/week @ 2023-09-27 6729/week @ 2023-10-04 14680/week @ 2023-10-11 13908/week @ 2023-10-18 13482/week @ 2023-10-25 11132/week @ 2023-11-01 9794/week @ 2023-11-08 4869/week @ 2023-11-15

42,049 downloads per month
Used in 19 crates (4 directly)

MIT license

68 lines

Force Send Sync

Tells the compiler things are Send and/or Sync.

Reasons not to use this crate

If you should not know what Send and 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 Send and/or Sync but 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.

No runtime deps