Secure context

[jfbastien]

Mozilla proposes doing HTTPS everywhere. We should consider what this means for WebAssembly, and discuss implications for all new features.

AI from CG-01-26, for everyone.

[lars-t-hansen]

Off the top of my head there are at least these gating points:

• new opcodes
• new flags (shared-memory flag; data-section inert/active flag)
• new syntax in the text format, eg, the 'shared' attribute on memory for the threads proposal
• host api changes (WebAssembly.Global constructor)
• changes in semantics, eg, the value -> WebAssembly.Global instance on the export object
• expansion of semantics, eg, strongly-typed tables

[littledan]

We might want to make a common decision about how this policy affects all programming languages, both JavaScript and WebAssembly, unless there's some relevant difference between them.