https://bugs.kde.org/show_bug.cgi?id=385341
Pearce Keesling changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=385341
--- Comment #3 from Jos van den Oever ---
There is code to convert std::string::String to QString and back. This always
requires a memory allocation because the encoding has to change between utf8
and utf16.
"QT seems to require that you do a begin_rem
https://bugs.kde.org/show_bug.cgi?id=385341
--- Comment #2 from Pearce Keesling ---
Something else I was wondering. Is there a particular reason that we're
requiring argument names? As far as I can tell there is never really a place
that those are needed from a developer's perspective. The Rust-C
https://bugs.kde.org/show_bug.cgi?id=385341
--- Comment #1 from Pearce Keesling ---
I've got most of the this solved. The only thing that's left as far as I can
tell is the interface going back from rust String to a QString. I'll need to
take a look at that when I get the time. I was able to make
https://bugs.kde.org/show_bug.cgi?id=385341
Pearce Keesling changed:
What|Removed |Added
CC||keesl...@gmail.com
--
You are receiving this