conrad-watt

5 ms·

1. 1.▲
   by conrad-watt 5y ago

   There is no problem, assuming that one believes that the list-of-USV abstraction (i.e. sanitising strings to be valid unicode) is the right thing to enforce at the component boundary, _including_ when the internals of the component are impl
2. 2.▲
   by conrad-watt 5y ago

   I agree with the linked quote - it captures an important reason why it is valuable to _enforce_ sanitisation at component boundaries, rather than merely documenting "please don't rely on isolated surrogates being preserved across
3. 3.▲
   by conrad-watt 5y ago

   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
4. 4.▲
   by conrad-watt 5y ago

   For reference, this is the lead maintainer of AS. You previously posted yourself that documenting sanitisation at the component boundary would be an acceptable solution: ( https://web.archive.org/web/20210726140105if_&#x
5. 5.▲
   by conrad-watt 5y ago

   Full disclosure, I am an active participant in WebAssembly standardisation, my github is here ( https://github.com/conrad-watt ). What follows is purely my personal opinion. This announcement is deliberately phrased to scare