Case Study: FFI Thread Safety
- Dominant language
- C++
- Stars
- 4
- Forks
- 2
- PR merge metrics
- PR metrics pending
Description
This case to be studied does not affect or influence the progress of the Zig project and its features.
Everything that is or will be tested has an experimental purpose.
**References**
- https://github.com/ziglang/zig/issues/8224
- https://github.com/ziglang/zig/issues/5962
- https://github.com/ziglang/zig/issues/9922
- https://github.com/ziglang/zig/issues/5311
- https://github.com/ziglang/zig/issues/12251
- https://github.com/ziglang/zig/issues/7769
**Related**
- https://github.com/kassane/tigerbeetle-cpp/issues/4
**asio - FFI**
- https://github.com/Heerozh/LuaAsio
- [Emilua - internal](https://docs.emilua.org/api/0.4/tutorial/internals.html) - @vinipsmaker project
**Others**
- [Vale & C - FFI safe](https://verdagon.dev/blog/fearless-ffi)
- [Asio and Threads](https://think-async.com/Asio/asio-1.28.0/doc/asio/overview/core/threads.html)
- [Strand](https://think-async.com/Asio/asio-1.28.0/doc/asio/overview/core/strands.html)
- [How strands work and why you should use them](https://www.crazygaze.com/blog/2016/03/17/how-strands-work-and-why-you-should-use-them/)
- https://github.com/chriskohlhoff/asio/issues/886
- https://github.com/chriskohlhoff/asio/issues/1408#issuecomment-1907081721
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.