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.

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 would guess a swappable battery would be separated from the vehicle, similar to a gas bottle for a grill.

The battery would be rented for a small deposit and on swapping you only pay the energy + service fee.

I guess you could also buy one to own, but then could not swap that.

That’s how it would make sense, at least.

Then why does the kernel have a crypto API?

Checkmate, Satoshi Torvalds!

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.