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
{{ message }}
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
An alternative I brought up during the meeting is:
usescript;// would obviously throw in any current context, Script or Moduleusemodule;// could be specced to be a no-op in a Module goal only
This would have the advantage that code with use module would definitely throw in every engine, unless it both had Module and use module noop support - whereas a "use module" pragma would not throw in anything that existed prior to pragma support.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
An alternative I brought up during the meeting is:
This would have the advantage that code with
use module
would definitely throw in every engine, unless it both had Module anduse module
noop support - whereas a"use module"
pragma would not throw in anything that existed prior to pragma support.The text was updated successfully, but these errors were encountered: