Why the fuck would they prevent private browsing? I use that a lot to be sure the session is closed correctly.
Why the fuck would they prevent private browsing? I use that a lot to be sure the session is closed correctly.
The idea is that I can see all the types in one glance, then I look at the rest.
It’s a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.
There are still obvious things the BC cannot get. For example:
struct Foo;
impl Foo {
fn num(&mut self) -> usize { 0 }
fn index(&mut self, _i: usize) { }
}
let foo = Foo;
foo.index(foo.num()); //error
Genuine question: what’s wrong with templating engines?
My coworkers do document the code:
/// Returns a list of foos, given a bar.
fn get_foos_from_bar(bar: Bar)
I really like this instance, so of course I’m 100% for the move
I’d argue the macros are quite bad:
I agree, though, that it’s better there’re here than nothing. It’s just that there is to be a better solution.
I think they just don’t like cringe
Sorry for the late answer. Those days, I’m interested in Ante. The language creator has some novel ideas for a non-GC memory safe language. And the compiler is written in Rust. It’s not finished at all tho.
I didn’t even know there were a survey (and I’ve used Rust professionnaly for years)
WTF I didn’t understand, thanks for the explanation. The fact that it’s used all around the world in big companies doesn’t matter I guess.