Explore >> Select a destination
|
You are here 
|
hackingcpp.com | ||
| | | | |
plv.mpi-sws.org
|
|
| | | | | ||
| | | | |
qsantos.fr
|
|
| | | | | This article will quickly explain the Rust types [T; N], &[T; N], &[T], Vec, &Vec with C code, and what the str, &str, String, OsString and CString add. Arrays and Slices Rust C [T; N] (array)Example: [i32; 100]Allocated on the stack T[N]Example: int[100]Allocated on the stack &[T; N] (array reference)Example: &[i32; 100]N is tracked at ... Continue reading Rust Strings for C Programmers ? | |
| | | | |
blog.dinaburg.org
|
|
| | | | | Update: jduck pointed out that the before/after code snippets were identical. Oops. Now fixed. I'd previously given up on C++ due to ... | |
| | | | |
rodusek.com
|
|
| | | Getting the name of a type in C++ is a hassle. For something that should be trivially known by the compiler at compile-time, the closest thing we have to getting the type in a cross-platform way is to use std::type_info::name which is neither at compile-time, nor is it guaranteed to be human-readable. In fact, both GCC and Clang actually return the compiler's mangled name rather than the human-readable name we are used to. Let's try to make something better using the modern utilities from c++17 and a little creative problem solving! | ||
