6c2819d8ba
When running in d8 the runtime flags need to be set by loading an SDK with the same name passed for the application that gets used when the application is started. If not the module system will create an additional instance of the SDK module. This meant the runtime flags were being set in one instance while the application read them from another. The same issue was present in the ddb script and this change fixes it there as well. Add the `--interop-null-assertions` option to the ddb script that uses the runtime flag to enable null checks on non-static JavaScript interop APIs. Issue: https://github.com/dart-lang/sdk/issues/55378 Change-Id: Id8c31383fa601f5953e2cc41021746aa918186b7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/361133 Reviewed-by: Srujan Gaddam <srujzs@google.com> Reviewed-by: Nate Bosch <nbosch@google.com> Commit-Queue: Nicholas Shahan <nshahan@google.com>