Andreas Woess

Could you please provide a complete, runnable reproducer?

@chumer: any conflicts that arise will have to be solved via an explicit suite import (override). I suppose we can have the dependencies command help do this automatically with a...

In the simplified dependency model, dynamic suite imports can still introduce version conflicts that can't be solved via an import in the parent suite. Such conflicts will have to be...

> What is the reason? What is the difference between standard "java.lang.System" class and my own class? That's simply because do not have a `net` package global (only `com`, `org`,...

Thank you for the report. We are aware of this unfortunate regression, which was caused by the removal of js from the base distribution. We will fix this in the...

We currently have no plans to add support for this, sorry.

Could you please rebase your changes on top of the latest master? There's been a few minor changes around iterator nodes that will have to be resolved. Namely, in a...

We've fixed (worked around) this issue for iterator-helpers by force-splitting `%IteratorHelperPrototype%.next`.

Related to this issue, I believe the following tests are also incorrect according to the current spec text: * [test/language/expressions/assignment/target-member-computed-reference-null.js](https://github.com/tc39/test262/blob/579268ab79e5ad6ca914c34f34ff4b136362c7e2/test/language/expressions/assignment/target-member-computed-reference-null.js) * [test/language/expressions/assignment/target-member-computed-reference-undefined.js](https://github.com/tc39/test262/blob/579268ab79e5ad6ca914c34f34ff4b136362c7e2/test/language/expressions/assignment/target-member-computed-reference-undefined.js) Namely, the test expects that at L49: `base[prop]...

Thank you for your contribution! This PR has already been merged in modified form (incorporating spec changes and resolving conflicts with changes in Graal.js). It is available under `--js.ecmascript-version=staging`. Consequently,...