It is an umbrella bug to keep track of BigInt work.
Also: https://bugs.webkit.org/show_bug.cgi?id=209782
I would like to add to this that BigInts don't appear to work as keys in ES Collections. I just took Safari 14 for a spin and ran into the most bizzare bugs where I could insert multiple entries with the same bigint keys in a Map. For example: const m = new Map() m.set(1n, 123) m.set(1n, 456) console.log(m) Map {1n => 123, 1n => 456} get(1n) undefined etc. Not sure what's up but it is broken.
(In reply to John Leidegren from comment #2) > I would like to add to this that BigInts don't appear to work as keys in ES > Collections. I just took Safari 14 for a spin and ran into the most bizzare > bugs where I could insert multiple entries with the same bigint keys in a > Map. > > For example: > > const m = new Map() > m.set(1n, 123) > m.set(1n, 456) > > console.log(m) > Map {1n => 123, 1n => 456} > > get(1n) > undefined > > etc. > > Not sure what's up but it is broken. This is fixed in https://trac.webkit.org/changeset/267373/webkit/. You can try it in STP 115 or later :)
Great! When will this be available to the general public? I'm unfamiliar with the release schedule of Safari but it looks to me that there will eventually be a Safari 14.1 release but that may take a while?
(In reply to John Leidegren from comment #4) > Great! When will this be available to the general public? I'm unfamiliar > with the release schedule of Safari but it looks to me that there will > eventually be a Safari 14.1 release but that may take a while? We cannot comment on future Apple software releases. After the fix is released, we can comment on that.
Ok, thanks anyway for the information. I'll wait patiently.