BigInt support

[Rudxain]

arr[n] where arr is an Array and n is a BigInt, is supported by Chromium. arr.at(n) throws an error because toInteger doesn't support BigInts

[zloirock]

arr[n] where arr is an Array and n is a BigInt, is supported by Chromium

Chromium 95:

Chrome 93:

FF Nightly:

FF91:

Spec draft:
https://tc39.es/proposal-relative-indexing-method/
Spec PR:
https://github.com/tc39/ecma262/pull/2493/files

Everywhere it throws an error on bigints. Why do you think that it should support BigInt?

[Rudxain]

If the at method didn't support BigInts, then one of the goals of the proposal would be incomplete (I'm talking about conciseness). Developers would have to write array.at(Number(x)) (where x is negative and within valid range) to get the same behavior as array[array.length - Number(y)] (where y == abs(x)). The following is a modification I made of the polyfill, it works on MS Edge Chromium (I haven't tested EdgeHTML) Version 93.0.961.47:

//github.com/tc39/proposal-relative-indexing-method#polyfill
function at(n) {
   n = Math.trunc(Number(n)) || 0; if (n < 0) n += this.length;
   return n < 0 || n >= this.length ? undefined : this[n]
};
const TypedArray = Reflect.getPrototypeOf(Int8Array);
for (const C of [Array, String, TypedArray]) {
   Object.defineProperty(C.prototype, "at", {value: at, writable: true, enumerable: false, configurable: true})
};

And I apologize for replying late, I didn't read my mail and didn't get a notification.

[zloirock]

core-js is a polyfill and should follow the spec. It's an issue for the proposal, you could write it here https://github.com/tc39/proposal-relative-indexing-method

[Rudxain]

Thanks for the info and your time. I didn't know I had to post it there. I'm relatively new to GitHub and got confused, sorry