This repository has been archived by the owner on Mar 7, 2021. It is now read-only.
make C strings a little more ergonomic #16
Comments
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
alex
added a commit
that referenced
this issue
Aug 20, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
std::ffi::CString
andstd::ffi:CStr
to work; they're actually in libstd, but I thinkCString
only uses alloc/containers andCStr
doesn't even need that. (And decide if we want it?)b"foo\0"
for compiile-time static C strings. Options include https://github.com/mzabaluev/rust-c-str and https://github.com/abonander/const-cstr (both of which usestd::ffi::CStr
) or just coding it ourselves as suggested in Consider adding CString/*const i8 literals rust-lang/rfcs#400 (comment) . If we write it ourselves I might argue for calling itc!
to keep it easy to read/write.The text was updated successfully, but these errors were encountered: