4 ms·
I'm curious what design led them to split code between two shared libraries but also require the state of them to be synchronized across calls to dlopen and dlc
by duped 1y ago
I'm curious what design led them to split code between two shared libraries but also require the state of them to be synchronized across calls to dlopen and dlclose. It sounds like that state should be in one library and not two.
- theamk 1y agothey kinda mention this - one of those is Rust, other is C++. My guess they made an all-new Rust plugin which used an existing C++ library. Pretty common case when existing code base is slowly being converted to rust.
- duped 1y agoBut why are they dynamically linking to each other?
- 01HNNWZ0MV43FF 1y agoI guess the C++ library might be binary-only or difficult to compile but, for curious readers, you can definitely link C++ and Rust into a single binary library or exe
- saurik 1y agoBut how/why is libA failing if libB has already been initialized? That's the thing which seems broken.