Rust has perfectly fine tools to deal with such issues, namely enums. Of course that cascades through every bit of related code and is a major pain.
Rust has perfectly fine tools to deal with such issues, namely enums. Of course that cascades through every bit of related code and is a major pain.
In the bottom picture it looks like the top “port” is just an air intake.
I hate thinking of usernames and I am extremely bad at it.
How can the ISP force their dns? They can’t know where you got the destination ip from.
There also isn’t a loop instruction though.
Not here, because it’s being used as a function argument.
It’s not even controllable RGB? Just shitty rainbow all the time?
Other way round: prefixes that contain “bi” are binary, so 1024-based.
The truth is that there is value in both a generalist and a specialist.
I think that’s fairly obvious with the smaller text and context.
Yeah I get it, it was just something I noticed. A pedantic lint, you could say.
I wanted to ask why it’s bad, what did you change?
Btw. the example function get_default is badly chosen, because unwrap_or_default exists.
And that 20 second delay really isn’t gonna impact the trip as a whole.
That is true. Therefore there shouldn’t be a problem with drivers driving a steady speed in the middle lane.
The rightmost lane is never completely free. And if it is, almost all drivers do use it.
What makes your right to go fast on the left lane more important than their right to go a reasonable ~120km/h in the middle lane?
Okay, I never looked at a truck’s speedometer. The point is they are overtaking just slightly faster.
It certainly feels like most trucks are going at least 90 km/h regularly.
The problem is that even in low traffic, there is a truck on the right lane every few meters. Often, after you switch to the right lane, someone decides to drive right next to you, forcing you to brake.
It’s just more comfortable to stay in the middle lane.
Now IMHO the real problem is when trucks are overtaking with 101km/h…
Not really, if absent means “no change”, present means “update” and null means “delete” the three values are perfectly well defined.
For what it’s worth, Amazon and Microsoft do it like this in their IoT offerings.