Welcome to the Lounge

Sander Rossel wrote:

You forgot shift, which removes the first element.

Sander Rossel wrote:

I just want to say array.remove(something); and it should remove something.

Sander Rossel wrote:

Everyone who says "splice is JavaScripts remove function" is dead wrong.

// given this
const data = [1, 2, 3, 4, 5];

// method 1, this is where you complain it takes two calls
delete data[2];
console.log(data.filter(x => x));

// method 2, this is where you complain it's not called "remove"
console.log(data.filter((x, i) => x !== 2));

// original method you didn't even bother to try, this mutates
// let me guess, never read the documentation on it?
data.splice(2, 1);
console.log(data);

// rounding off to two decimal places
1.005.toFixed(2); // outputs 1 instead of 1.01
Math.round(1.005 * 100) / 100; // outputs 1 instead of 1.01

Jeremy Falcon wrote:

complete accuracy on numbers

Matt Bond wrote:

When seeking consistency, I would wrap all of that in a utility class. This way I know it's consistent and works the same everywhere. If I need something a little different, then I either overload or add a default parameter as the occasion requires.

Matt Bond wrote:

I agree that storing the numerator and denominator would be the best way to prevent most headaches. In C#, I would use a Fraction struct for this (home grown if one doesn't exist already). Only collapse the fraction to a primitive type as necessary. This also has the benefit of letting you use money with a decimal value, so you don't have to do the extra math to get the cents back.

Matt Bond wrote:

Speaking of money, you only have to store 4 decimals with money to be accurate for accounting purposes.

Matt Bond wrote:

However, we don't do multiplication and division on the money.

decimal result = decimal(1.0) * decimal(2.0); // answer is "0.3"

double resulta = Math.Round(x + y, 5); // 5 indicates precision (answer is "0.3")