-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Es6 (mostly built-ins) #180
Conversation
# Conflicts: # runtime_test.go
Proxy, Reflect, new.target, tons of refactoring. Co-authored-by: noctarius <[email protected]>
* Enabled travis build on s390x (which is big endian)
Implemented ArrayBuffer, DataView and the typed arrays.
# Conflicts: # builtin_array.go
…re not guaranteed to remain the same).
…speed to strconv.FormatFloat().
# Conflicts: # vm.go
# Conflicts: # object_goreflect.go # object_goreflect_test.go
# Conflicts: # builtin_json.go
…rn the original Value)
…d that existed in the master.
Hi @dop251, Here are all the results and this are the changes to corejs, I did, to get them. The important thing is the difference between k6 + corejs and k6 with es6 without corejs (the other is there for completeness). I am pretty sure at least some of the Here is the output of
I will try to run the whole test suite with the more intricate tests in the coming days |
Hi. Thanks for running those. Can you make it report exactly which test has failed? There may be some genuine issues worth fixing (like the one with sort), but it's hard to tell without knowing more details. I just tried running equivalent tests for Array.prototype.concat and they all look fine to me. I can see there is a bunch of stuff that is post-es6 (esnext.*), as well as Annex B extensions (like es.string.blink) which I doubt anyone uses... |
I went through the ones that fail with es6 but not with corejs 2.5.1 and aren't obviously not interesting (like the blink stuff or reflect metadata (which has been dropped as far as I can see)). I haven't checked that this is the actual expected behavior in the spec ... :D
Should return 1 ... apparently ... here the test has other parts so I expect this doesn't work in other ways as well
|
@dop251 changes from f197596 to 3ec8e20
some weren't in core-js 2.5.1 so compared to it, this are the one es6 fails while corejs 2.5.1 passes and arent't esnext
|
All these are missing post es6 functionality. I'm going to do the merge now I think... |
No description provided.