From: Sean Lynch <sean@seanplynch.com>
To: guile-devel@gnu.org
Cc: Sean Lynch <sean@seanplynch.com>
Subject: [PATCH 0/4] Support ECMAScript Test262 Assertion Harness
Date: Wed, 28 Oct 2020 00:03:27 -0400 [thread overview]
Message-ID: <20201028040330.22051-1-sean@seanplynch.com> (raw)
Hello all,
I've been hacking a bit on the ECMAScript implementation and thought it
might be useful to be able to run the ECMAScript Test262 test suite, so
I implemented just enough to be able to load the assertion harness
required by all tests. I thought I'd check in to see if there was any
interest in merging these changes.
The relevant harness files can be found here:
https://github.com/tc39/test262/blob/main/harness/sta.js
https://github.com/tc39/test262/blob/main/harness/assert.js
I plan to slowly use the test suite as a guide to increasing the
ECMAScript coverage, and as such if anyone has any thoughts about other
improvements to the ECMAScript compiler I would be all ears!
Happy Hacking!
Sean
Sean Lynch (4):
Support ecmascript return operator with no operand.
Implement ecmascript try/catch.
Implement ecmascript function prototype.
Fix some reserved word usages in ecmascript implementation
.../language/ecmascript/compile-tree-il.scm | 39 +++++++--
module/language/ecmascript/function.scm | 7 +-
module/language/ecmascript/impl.scm | 18 +++-
module/language/ecmascript/parse.scm | 51 +++++++++--
module/language/ecmascript/tokenize.scm | 84 +++++++------------
5 files changed, 130 insertions(+), 69 deletions(-)
--
2.29.1
next reply other threads:[~2020-10-28 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 4:03 Sean Lynch [this message]
2020-10-28 4:03 ` [PATCH 1/4] Support ecmascript return operator with no operand Sean Lynch
2020-10-28 4:03 ` [PATCH 2/4] Implement ecmascript try/catch Sean Lynch
2020-10-28 4:03 ` [PATCH 3/4] Implement ecmascript function prototype Sean Lynch
2020-10-28 4:03 ` [PATCH 4/4] Fix some reserved word usages in ecmascript implementation Sean Lynch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201028040330.22051-1-sean@seanplynch.com \
--to=sean@seanplynch.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).