Also, Rust, Java, .NET, glib, and several other languages, runtimes, and
frameworks **require** that **all** code must be thread-safe, full stop. A
Java or .NET VM will *always* have multiple threads running, and a GTK or QT
application must assume that it will. Using the RPM transaction APIs from such
a process is currently Undefined Behavior. Rust programs are not all
multi-threaded, but Rust libraries are required to work in multithreaded
programs, which means that the librpm.rs bindings are probably unsound.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1526#issuecomment-773509614
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
