[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, 2 insertions, 2 deletions

diff --git a/rust/src/collaboration/user.rs b/rust/src/collaboration/user.rs
index 6b490942..51bdebb5 100644
--- a/rust/src/collaboration/user.rs
+++ b/rust/src/collaboration/user.rs
@@ -48,7 +48,7 @@ impl RemoteUser {
     }
 
     /// Set user's username. You will need to push the user to update the Remote
-    pub fn set_username<U: IntoCStr>(&self, username: U) -> Result<(), ()> {
+    pub fn set_username(&self, username: &str) -> Result<(), ()> {
         let username = username.to_cstr();
         let result =
             unsafe { BNCollaborationUserSetUsername(self.handle.as_ptr(), username.as_ptr()) };
@@ -67,7 +67,7 @@ impl RemoteUser {
     }
 
     /// Set user's email. You will need to push the user to update the Remote
-    pub fn set_email<U: IntoCStr>(&self, email: U) -> Result<(), ()> {
+    pub fn set_email(&self, email: &str) -> Result<(), ()> {
         let username = email.to_cstr();
         let result =
             unsafe { BNCollaborationUserSetEmail(self.handle.as_ptr(), username.as_ptr()) };