Remove source phase resolution time negative error types

[legendecas]

The source phase import binding name tests can be tested more easily with the resolution time negative error types removed, as they are host defined errors.

Refs: #4121 (comment)

[nicolo-ribaudo]

Instead of doing this, can we just remove type: SyntaxError? We just need to assert that we are getting an error at resolution time, regardless or where it comes from, since we are just checking that it does not throw when parsing.

This is to avoid having to require another flag, which may prevent some implementations from running the test.

[legendecas]

Instead of doing this, can we just remove type: SyntaxError?

Updated. Thanks for suggestion, sounds like a good alternative to me.

[nicolo-ribaudo]

Looks good, if Error is something valid to write there to mean "any error"

[Ms2ger]

Looks good, if Error is something valid to write there to mean "any error"

Hm, I'm not sure that it is.

type - If an error is thrown, it is implicitly converted to a string. In order for the test to pass, this value must match the name of the error constructor.

[nicolo-ribaudo]

Can we just omit type?

[legendecas]

Can we just omit type?

No, the linter complains about missing type:

test262/tools/lint/lib/checks/negative.py

Line 26 in 75fddbd

return '"negative" must specify a "type" field'

[nicolo-ribaudo]

Then what about completely moving those tests to _FIXTURE files, and add an entrypoit that does

import("./the-actual-entrypoint_FIXTURE.js").then(() => $DONE(new Error("It should have failed")), () => $DONE());

[legendecas]

Updated and verified with d8.