C-string manipulation and management
This modules provides the basic methods for creating and manipulating null-terminated strings for use with FFI calls (back to C). Most C APIs require that the string being passed to them is null-terminated, and by default rust's string types are not null terminated.
The other problem with translating Rust strings to C strings is that Rust strings can validly contain a null-byte in the middle of the string (0 is a valid Unicode codepoint). This means that not all Rust strings can actually be translated to C strings.
A C string is managed through the
CString type defined in this module. It
"owns" the internal buffer of characters and will automatically deallocate the
buffer when the string is dropped. The
ToCStr trait is implemented for
&[u8], but the conversions can fail due to some of the limitations
This also means that currently whenever a C string is created, an allocation must be performed to place the data elsewhere (the lifetime of the C string is not tied to the lifetime of the original string/data buffer). If C strings are heavily used in applications, then caching may be advisable to prevent unnecessary amounts of allocations.
Be carefull to remember that the memory is managed by C allocator API and not by Rust allocator API. That means that the CString pointers should be freed with C allocator API if you intend to do that on your own, as the behaviour if you free them with Rust's allocator API is not well defined
A generic trait for converting a *const c_str to another Rust type
A generic trait for converting a value to a CString.
External iterator for a CString's bytes.