4 Commits

Author	SHA1	Message	Date
Joe Savona	90348cc873	[housekeeping] Remove disabled test262 setup ... I sincerely appreciate the effort to get test262 up and running. This was my idea, it seemed like a really good way to test our correctness on edge cases of JS. Unfortunately test262 relies heavily on a few specific features that we don't support, like classes and `var`, which has meant that we never actually use this as a test suite. In the meantime we've created a pretty extensive test suite and have tools like Sprout to test actual memoization behavior at runtime, which is the right place to invest our energy. Let's remove?	2024-01-12 12:26:30 -08:00
Jan Kassens	f6f042d747	Switch test262 submodule to https url ... I had trouble checking out the repo using Sapling because the submodule couldn't clone properly. I got > Error: Permission denied (publickey) In my branch I tested that the https URL format seems to work okay with Sapling.	2024-01-12 15:07:24 -05:00
lauren	a0dc166991	[rfc] Remove top level forget directory ... Sorry about the thrash in advance! This removes the top level `forget` directory which adds unnecessary nesting to our repo Hopefully everything still works	2023-08-22 15:04:54 -04:00
Lauren Tan	9027117c4f	Scaffolding for test262 ... - Adds a shallow git submodule for test262 as the tests aren't available as an npm module - To run all tests: `yarn test262:all`. Note that this chunks up the tests by test262 folder as there are over 50k+ tests and the test harness only accepts arrays of filepaths which exceeds arg limits - To run a specific test: `yarn test262 test262/test/folder/file.js`. You can also pass globs which expand into an array of filepaths: `yarn test262 test262/test/folder/**/*.js` - More instructions for the test-harness can be found here: https://github.com/bterlson/test262-harness	2022-11-15 13:24:14 -05:00