I don't think that casting a range of bits as some other arbitrary type "is a bug nobody sees coming".

C++ compilers also warn you that this is likely an issue and will fail to compile if configured to do so. But it will let you do it if you really want to.

That's why I love C++

you are viewing a single comment's thread
view the rest of the comments

[–] merc@sh.itjust.works 4 points 4 days ago (1 children)

I've seen this a bunch in 3rd party library headers, sadly. So it ultimately doesn't matter how good my code is.

Yeah, I've seen that too. The problem is that once the library starts spitting out warnings it's hard to spot your own warnings.

[–] dejected_warp_core@lemmy.world 4 points 4 days ago

Yuuup. Makes me wonder if there's a viable "diaper pattern" for this kind of thing. I'm sure someone has solved that, just not with the usual old-school packaging tools (e.g. automake).