You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IIRC in the old design realm.import(str) returns a { module: Namespace } to prevent auto-unpacking of thenable object in Promise. It seems like this behavior is removed in the current spec. Is it no longer to be considered to be a problem?
exportfunctionthen(){console.log('oops')}
The text was updated successfully, but these errors were encountered:
We have informal consensus among Compartments champions that we can and should make import consistent with dynamic import per the principle of least surprise. The hazard exists. Dynamic import is unfixable. Better in this case to be consistent.
The Compartment proposal has a synchronous module method that is not vulnerable to the thenable module hazard and can be used in concert with import to avoid the problem.
IIRC in the old design
realm.import(str)
returns a{ module: Namespace }
to prevent auto-unpacking ofthenable
object in Promise. It seems like this behavior is removed in the current spec. Is it no longer to be considered to be a problem?The text was updated successfully, but these errors were encountered: