4 commits

Author	SHA1	Message	Date
Johannes Altmanninger	c6756e9324	Canonicalize some wide string imports ... wchar.rs should not import let alone reexport FFI strings. Stop re-exporting utf32str! because we use L! instead. In wchar_ffi.rs, stop re-exporting cxx::CxxWString because that hasn't seen adoption. I think we should use re-exports only for aliases like "wstr" or for aliases into internal modules. So I'd probably remove `pub use wchar_ffi::wcharz_t = crate::ffi::wcharz_t` as well.	2023-03-05 10:32:20 +01:00
Mahmoud Al-Qudsi	562eeac43e	Port job_group to rust (#9608) ... More ugliness with types that cxx bridge can't recognize as being POD. Using pointers to get/set `termios` values with an assert to make sure we're using identical definitions on both sides (in cpp from the system headers and in rust from the libc crate as exported). I don't know why cxx bridge doesn't allow `SharedPtr<OpaqueRustType>` but we can work around it in C++ by converting a `Box<T>` to a `shared_ptr<T>` then convert it back when it needs to be destructed. I can't find a clean way of doing it from the cxx bridge wrapper so for now it needs to be done manually in the C++ code. Types/values that are drop-in ready over ffi are renamed to match the old cpp names but for types that now differ due to ffi difficulties I've left the `_ffi` in the function names to indicate that this isn't the "correct" way of using the types/methods.	2023-02-25 16:42:45 -06:00
Xiretza	333056a9ec	rust: add bindings for signal conversion functions	2023-02-18 18:53:50 +01:00
ridiculousfish	d843b67d2d	Initial Rust commit	2023-02-02 19:34:47 -07:00