| 18:17 | <ptomato> | hi, test262 would appreciate some feedback on whether this requirement would potentially be a problem for your test262 runners: https://github.com/tc39/test262/pull/4398/commits/6ccad34e9b2e2119d39e889be48fd592ef07ef2e |
| 18:52 | <shu> | evaluating the scripts in order of inclusion is actually required currently by the v8 runner |
| 18:54 | <shu> | since these helper scripts define globals, the two reasonable options i see are either requiring they be evaluated in order, or that no helper script can assume any other helper script has run (e.g. can't use assert functions or anything) |
| 19:23 | <ptomato> | the interpreting instructions already do specify that assert.js and sta.js must be run first regardless of other helper scripts, so there are a few things including asserts that can be assumed to be present in helper scripts |
| 19:27 | <ptomato> | another reasonable option would be to allow helper scripts to import other helper scripts. but I don't see a reason to do that right now |
| 19:36 | <bakkot> | my runner does not support esm so I would like to avoid having the helpers depend on imports/exports |
| 19:36 | <bakkot> | the evaluation order requirement is fine for me |
| 21:58 | <ptomato> | by "import" I meant "fake import using includes in the helper frontmatter"; sorry, should've been clearer about that |
| 21:58 | <shu> | yes, but some helpers introduce their own special asserts |
| 21:58 | <shu> | as was the case with the SM-imported tests that surfaced this issue |
| 22:05 | <ptomato> | I see what you mean, yes that's right |
| 22:10 | <bakkot> | ah, gotcha. I want to avoid that because I don't read the frontmatter for the harness files but it is certainly technically feasible if that becomes necessary |