From 6264254065bbae9d89f51cf3330379b7ace09592 Mon Sep 17 00:00:00 2001
From: Mason Reed <mason@vector35.com>
Date: Sat, 3 May 2025 23:15:17 -0400
Subject: [Rust] Return `String` instead of `BnString` for cases where lossy
 conversion can be tolerated

Still need to go and audit all usage, but realistically the most important places to give the user control are with symbols, where the data can come from non utf8 sources

This is still incomplete, I just looked for usage of -> BnString so any other variant was omitted.
---
 rust/src/calling_convention.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'rust/src/calling_convention.rs')

diff --git a/rust/src/calling_convention.rs b/rust/src/calling_convention.rs
index 2fb282e0..6f2e9a1c 100644
--- a/rust/src/calling_convention.rs
+++ b/rust/src/calling_convention.rs
@@ -455,8 +455,8 @@ impl CoreCallingConvention {
         })
     }
 
-    pub fn name(&self) -> BnString {
-        unsafe { BnString::from_raw(BNGetCallingConventionName(self.handle)) }
+    pub fn name(&self) -> String {
+        unsafe { BnString::into_string(BNGetCallingConventionName(self.handle)) }
     }
 
     pub fn variables_for_parameters(
-- 
cgit v1.3.1