Closed michaelficarra closed 10 months ago
Ping @jhnaldo. We'd like to merge https://github.com/tc39/ecma262/pull/3194, but it's currently blocked on this change. If we don't hear back soon, we'll have to disable esmeta checks in our CI until esmeta is updated.
Hi @michaelficarra. I'm sorry for the inconvenience. I will fix the error you mentioned this week and ping you after doing it.
Dear @michaelficarra. I fixed bug this issue in this commit https://github.com/es-meta/esmeta/commit/1401b396a4a37455712010cf61595e1aaccfc009 and applied it in the new release version ESMeta v0.3.3. I will create a PR for this new update.
In https://github.com/tc39/ecma262/pull/3194, we are renaming "Integer-Indexed exotic object" to "TypedArray". When running esmeta type checking in our CI, we get the following error:
Error: Exception in thread "main" java.util.NoSuchElementException: key not found: IntegerIndexedExoticObject.GetOwnProperty
I think there may have been some special handling of IIEOs and hopefully the fix will be a simple name change on your side to match our new name.