Personally I don’t like unit tests. I’d rather have debug asserts and larger scope tests.

But using unit tests as debugging is near too

Ignoring the AI stuff, I don’t even get the joke.

What’s this?

True. Doesn’t solve the other issue tho. Heck, I work on rust a lot, and rustrover is free

NGL I’d use jetbrainz products more if they weren’t that pricey and more portable

Big “don’t help just film” vibes here

Wait that’s AI!? I thought it was a random edited image from the internet

What is the original? I didn’t saw any ai slop on my feed

BTW you need more lights ;)

What

And of course the ai put rail signals in the middle.

Chain in, rail out. Always

!Factorio/Create mod reference if anyone is interested !<

You need to restart your introvert. It’s clearly softlocked

Good and bad use-cases for floats

Floats can be used everywhere where it doesn’t matter that you can’t store a 100% accurate base ten representations. For example positions and speeds in 3D games and animations, “analog” values like temperatures, speed of a vehicle, geo positions with longitude and latitude, a persons weight or heart pressure. In fact if you develop games there is no way around 32 bit floats because GPUs are f32 number crunching beasts. Modern 3D games wouldn’t be possible without all those fast f32 calculations.

You shouldn’t use binary floats if you need or expect accurate base ten calculations (addition, subtraction, multiplication, - note that divisions also introduce errors quickly in decimal types) and for dimensions that have a smallest unit that can’t be broken down, for example like money. If you need to handle money just store the amount of cents as integers and only divide by 100 in your display function.

This is exactly my point. Don’t use floats when you need to get accurate stuff, but use it when you need a “feel” for it

if true

To whoever does that, I hope that there is a special place in hell where they force you to do type safe API bindings for a JSON API, and every time you use the wrong type for a value, they cave your skull in.

Sincerely, a frustrated Rust dev

Floats are only great if you deal with numbers that have no needs for precision and accuracy. Want to calculate the F cost of an a* node? Floats are good enough.

But every time I need to get any kind of accuracy, I go straight for actual decimal numbers. Unless you are in extreme scenarios, you can afford the extra 64 to 256 bits in your memory

From someone in computer networking classes: “I don’t use GitHub. This is too complicated” Like bruh. The instructions are right there in the readme.

There’s also the time where we were asked to read temperature from a sensor, and everyone went straight to chatgpt. Meanwhile, first search result, full repo with full noob instructions.