-
Updated
Dec 3, 2020 - C++
zero-copy
Here are 46 public repositories matching this topic...
-
Updated
Dec 2, 2020 - Rust
-
Updated
Nov 27, 2020 - C++
-
Updated
Jun 28, 2019 - C
Empty slices and strs will still align writers, which can potentially waste space. Instead, they should point to the start of the archive (pos 0).
-
Updated
Feb 9, 2018 - C#
-
Updated
Nov 4, 2018 - C++
-
Updated
Oct 24, 2017 - C++
-
Updated
Dec 2, 2020 - Rust
-
Updated
Feb 3, 2019 - Go
-
Updated
Oct 24, 2020 - Rust
-
Updated
Feb 3, 2020 - C
-
Updated
Oct 28, 2020 - C++
-
Updated
Apr 1, 2019 - Pony
-
Updated
Oct 28, 2020 - Rust
-
Updated
Mar 23, 2017 - C
-
Updated
May 24, 2018 - Java
-
Updated
Apr 19, 2018 - C
-
Updated
Mar 4, 2017 - Java
-
Updated
Oct 27, 2020 - C++
-
Updated
Dec 2, 2020 - C
Improve this page
Add a description, image, and links to the zero-copy topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the zero-copy topic, visit your repo's landing page and select "manage topics."


Brief feature description
Iceoryx uses a variety of strings (
std::string,cxx::string<>,cxx::CString100, etc).Once #253 is merged this mishmash should be cleaned-up.
Detailed information
Only use
cxx:string<>or types created from it.No std::string in public API
No more std::strings in code base