This is my experience every time I return to learning rust. I’m guessing that if I used it more often than once a quarter with hobby projects I’d stop falling into the same traps.
kamikazerusher
Ok, I did not expect that ending
I don’t disagree that bombing Iran puts us at risk of starting a war we don’t want to be involved in. However I think the public is too split on the matter to put majority support behind impeachment.
Conservative circles themselves appear divided with some saying the display of force was necessary and avoided direct conflict (minimizing operational costs), some saying the President is authorized to conduct these actions under the War Powers Resolution of 1973, and some voicing dissent or disapproval altogether of this action.
The War Powers Resolution will probably be the loophole that conservative outlets use to claim that Trump has done nothing wrong. I don’t know if there’s been an exercise of this authority without congressional approval that has lead to the targeted country declaring war as a result. If this were to happen, maybe there will be clear grounds to impeach, but I don’t think the public will display a majority support for it to happen.
Yeah I was surprised by this this morning when I logged into my .ee account. But I get it. Burnout is no fun and moderating/administrating can be a thankless position that eats into your time.
Eh, I’m not entirely sold on that idea.
I think they do a good job of pointing out “this is a behavior/feature of Rust you need to understand.” However they can send you down the wrong path of correction.
The compiler error mentioning static lifetime specifiers of
&str
demonstrates both. It indicates to the developer that ownership and scopes will play a significant role when defining and accessing data. The error though will guide them towards researching how to define static lifetimes and possibly believe that they will need to set this in their functions and structs. Each time you look at questions about this error in places like Stack Overflow with example code you’ll find suggested solutions explaining that a manually-defined static lifetime isn’t necessary to resolve the problem.