[Rust] Reduce usage of `IntoCStr` in function signatures

This is being done to reduce complexity in function signatures, specifically many of the strings we are passing ultimately should be new types themselves instead of "just strings", things such as type ids.

Another place which was confusing was dealing with filesystem related APIs, this commit turns most of those params into a stricter `Path` type.

This is bringing the rust api more inline with both python and C++, where the wrapper eagerly converts the string into the languages standard string type.

Special consideration must be made for symbols or other possible non utf-8 objects.

This commit will be followed up with one that adds the `IntoCStr` bound on API's we want to keep as invalid utf-8 so we can for example, get section by name on a section with invalid utf-8.

1 files changed, 4 insertions, 4 deletions

diff --git a/rust/src/disassembly.rs b/rust/src/disassembly.rs
index 396bcfcc..973fd57c 100644
--- a/rust/src/disassembly.rs
+++ b/rust/src/disassembly.rs
@@ -1242,13 +1242,13 @@ impl DisassemblyTextRenderer {
         unsafe { Array::new(tokens, count, ()) }
     }
 
-    pub fn wrap_comment<S1: IntoCStr, S2: IntoCStr, S3: IntoCStr>(
+    pub fn wrap_comment(
         &self,
         cur_line: DisassemblyTextLine,
-        comment: S1,
+        comment: &str,
         has_auto_annotations: bool,
-        leading_spaces: S2,
-        indent_spaces: S3,
+        leading_spaces: &str,
+        indent_spaces: &str,
     ) -> Array<DisassemblyTextLine> {
         let cur_line_raw = DisassemblyTextLine::into_raw(cur_line);
         let comment_raw = comment.to_cstr();