Having to run a debugger to know what gets called at a given time is awful, and this oop practices exacerbate this
Miaou
Well the ones from France don't seem to do much, maybe the other ones are worse
I agree with your point, but you're arguing that noise can be redundant data. I am arguing that redundant data is not necessarily noise.
In other words, a signal can never be filtered losslessly. You can slap a low pass filter in front of the signal and call it a day, but there's loss, and if lossless is a hard requirement then there's absolutely nothing you can do but work on compressing redundant data through e.g. patterns, interpolation, what have you (I don't know much about compression algos).
A perfectly noise free signal is arguably easier to compress actually as the signal is more predictable.
Ugh? That's not what it means at all. Compression saves on redundant data, but it doesn't mean that data is noise. Or are you using some definition of noise I'm not aware of?
What I meant is, the former can be a genuine mistake, the latter is a conscious (probably uneducated) decision
I spent my day today setting up nginx with mtls at work, and I actually think it's a great approach for what op is trying
Rust has a warning (has it been promoted to error? I think it was supposed to be) about comparing floats. Nothing to do with same being const. You basically don't have an equality operator for them
They wouldn't be running into an issue, but creating one, that's different
Then most people shouldn't be writing code, I don't know what else to tell you, this is probably one of the first thing you learn about FP arithmetic, and any decent compiler/linter should warn you about that.
Idiots downvoting you (c/technology...) but this how e.g. Haskell and rust handle that, and probably most strongly typed languages
My bad I misunderstood what you meant
Still this is what DNT is for but no one honours that, and it's not the EU's fault
I have the same problem with oop. 10 levels of encapsulated calls just to see you were in an overridden methods without enough data to find out which implementation it was. Ugh