An Urgent Notice from AssemblyScript

• interface-types

  14 615 3.1 WebAssembly

  

  This seems to be the discussion thread related to this.

  https://github.com/WebAssembly/interface-types/issues/13

• assemblyscript

  6 13,968 8.7 WebAssembly

  A TypeScript-like language for WebAssembly.

  

• SonarQube

  www.sonarqube.org

  sponsored

  Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.

  

• design-principles

  3 109 5.4 Makefile

  A small-but-growing set of design principles collected by the TAG while reviewing specifications

  

  I don't agree with your representation that sanitisation of isolated surrogates constitutes "corruption". As a high-level point, when passing a string from your component to an external one, the external component receives a sanitised copy of your string - the original string is not modified in-place. So you still have access to your original string if you're relying on the presence of isolated surrogates for some reason.

  For fairness, I will link below to your concrete example of "corruption", noting that you claim it will render Wasm "the biggest security disaster man ever created for everything". The fundamental bug is in splitting a string at a point which happens to be between two code points which make up an emoji. This kind of mistake can already cause logic and display errors in other parts of the code (e.g. for languages with non-BMP characters) independent of whether components are involved.

  https://github.com/w3ctag/design-principles/issues/322

Suggest a related project