When returning an immutable reference to a private struct field. (On mobile and used vertical bars instead of a bunch of HTML codes)
When returning an immutable reference to a private struct field. (On mobile and used vertical bars instead of a bunch of HTML codes)
A vec and a string are basically the same thing (a series of bytes)
In the context of vectors I prefer my APIs to return an empty set rather than an None-option. This makes handling it much easier because you can still iterate over it, it just has nothing.
This might involve the compiler making an allocation of an empty array but most of them (gcc, ghc) will now what you are doing and optimize the null check on the empty array to a bool check.
Note: the
ᐸᐳ
characters used below are Canadian Aboriginal syllabics because Lemmy devs haven’t fixed broken input sanitization yet.Everything is a series of bytes! I thought you were going to mention that both are fat pointers. But that “series of bytes” description is quite weird.
This is not a valid consideration/objection, as
Option
s are iterable and you can flatten them:fn main() { let v = vec![1,2,3]; for n in Some(&v).into_iter().flatten() { eprintln!("{n}"); } for n in None::ᐸ&Vecᐸi32ᐳᐳ.into_iter().flatten() { eprintln!("{n}"); } }
This paragraph appears to be out of place in the context of a Rust discussion.
Yes, but it’s a pain to iterate over Options of Vec because you need to check/flatten twice. I am aware gcc/ghc is not relevant to rust discussions but I am not sure if rustc performs these specific optimizations. I expect it does because they are trivial. Who knows. I am just some random dude on the internet and a lot of drugs.
@heartlessevil @RunAwayFrog Yeah, LLVM’s got your back.
Vec::new is const and thus can’t allocate anyways.