#Frustrations with QuickJS

1 messages · Page 1 of 1 (latest)

zinc belfry
#

It's well known that there are holes missing in QuickJS over, say, V8. Especially with missing APIs.

But what about engine stuff, like evaluation order? For example, I hit a wall earlier where static properties on a class couldn't make new instances of that class. That works on V8, as the class is made available before such static properties are evaluated.

Any other weird edge cases I need to know about? I'd normally just look up QuickJS stuff on Google, but it's kinda harder to look anything up on QuickJS.

vagrant path
#

Ya, there are differences, the case with instances on static fields is not ECMAScript specifications so it ok, thats is not supported, there are also some changes to running the async corutines in MC Engine its nut base QuickJS, but its little bit modified, for example, the async implementation, corutines have to fit somehow into the single minecraft ticks, so there are some changes what cant be searched on internet as well. Another example is BigInt, its not supported at all, but QuickJS has it right?
You can check the Engine Environment on Bedrock Wiki for some detials

tawny musk
#

finally someone replied