I don’t want a single application that just works for a few cases but doesn’t work for tons of other cases. With such a world we would have a Windows OS where you need to use Face-ID for everything you want to use and sometimes just crashes and restricts the usage of something simple stupid because you don’t have the magical Windows Battlepass or smth.
I also have the same new look in Slovenia. Since Chipolo is Slovenian company, I will just drive to Chipolo company to get it and then wait for Android Find My Devicu update 😝 just kidding
Nice. I made the mistake of popping into KFC for a rice box yesterday. There was a kid screaming at the top of it’s lungs. Fortunately I had my IEMs with me!
I think that’s the only thing I dislike about rust. Not having to use * to dereference but later having to use is tad confusing. I know it’s still clever solution but in this case I prefer c++'s straightforward consistency.
C++ does have the problem that references are not objects, which introduces many subtle issues. For example, you cannot use a type like std::vector<int&>, so that templated code will often have to invoke std::remove_reference<T> and so on. Rust opts for a more consistent data model, but then introduces auto-deref (and the Deref trait) to get about the same usability C++ has with references and operator->. Note that C++ will implicitly chain operator-> calls until a plain pointer is reached, whereas Rust will stop dereferencing once a type with a matching method/field is found. Having deep knowledge of both languages, I’m not convinced that C++ features “straightforward consistency” here…
honestly with Go in general I’m in a perpetual cycle of being annoyed with it and then immediately being amazed when I find some little trick for efficiency - with stringer interfaces and the like
Same for C, & yields a pointer to a value, and * allows you to access the data. (For rust people, a pointer is like a reference with looser type checking)
feddit.uk
Oldest