4 ms·

Thanks! Here's a quick summary from there, with links to the implemented proposals. Multiple values: Generalized the result type of blocks and functions to all

Thanks! Here's a quick summary from there, with links to the implemented proposals. Multiple values: Generalized the result type of blocks and functions to allow for multiple values; in addition, introduced the ability to have block parameters https://github.com/WebAssembly/spec/blob/main/proposals/multi-value/Overview.md https://github.com/WebAssembly/spec/blob/main/proposals/mult... Reference types: Added and as new value types and respective instructions Table instructions: Added instructions to directly access and modify tables Multiple tables: Added the ability to use multiple tables per module Bulk memory and table instructions: Added instructions that modify ranges of memory or table entries https://github.com/WebAssembly/spec/blob/main/proposals/reference-types/Overview.md https://github.com/WebAssembly/spec/blob/main/proposals/refe... https://github.com/WebAssembly/spec/blob/main/proposals/bulk-memory-operations/Overview.md https://github.com/WebAssembly/spec/blob/main/proposals/bulk... Vector instructions: Added vector type and instructions that manipulate multiple numeric values in parallel (also known as SIMD, single instruction multiple data) https://github.com/WebAssembly/spec/tree/main/proposals/simd/ https://github.com/WebAssembly/spec/tree/main/proposals/simd... Sign extension instructions: Added new numeric instructions for performing sign extension within integer representations. https://github.com/WebAssembly/spec/blob/main/proposals/sign-extension-ops/Overview.md https://github.com/WebAssembly/spec/blob/main/proposals/sign... Non-trapping float-to-int conversions: Added new conversion instructions that avoid trapping when converting a floating-point number to an integer https://github.com/WebAssembly/spec/blob/main/proposals/nontrapping-float-to-int-conversion/Overview.md https://github.com/WebAssembly/spec/blob/main/proposals/nont...

dmitriid 4y ago
So it looks like it's basically slapping a 2.0 on standardized features from the roadmap: https://webassembly.org/roadmap/ https://webassembly.org/roadmap/
- richdougherty 4y ago
  I think that's the process, yes. Features get proposed, discussed, implemented, then eventually when they're done they're moved into the spec and tagged with a version.
  - dmitriid 4y ago
    Just realised this will make it easier for tools like caniuse. Instead of listing all features, they can just have "webgpu 2.0 availability"
tomcam 4y ago
Appreciate this. Can you explain why there appear to be English-looking letters used for terms but with alternate Unicode versions? Makes everything look jumbly but I'm sure there's a good reason.
- richdougherty 4y ago
  Are you talking about the MathJax rendering used for instruction names?
  - tomcam 4y ago
    False alarm. I think it's a font rendering problem on Safari. When I tried Chrome and Firefox it didn't appear. For example, under "External Types" at https://www.w3.org/TR/wasm-core-2/syntax/types.html#external-types https://www.w3.org/TR/wasm-core-2/syntax/types.html#external... you see this grammar rule: externtype ::= func functype | table tabletype | mem memtype | global globaltype On Safari, the tokens fun, table, men, and global render with weird font baselines on some letters: c, o, e and a are raised a few points higher than they should be. I just figured these were odd substitutions for ASCII characters from further in the Unicode alphabet, maybe to avoid collisions with other reserved token names or something (vamping here because it was all I could think of). Sorry about that.
    - cormacrelf 4y ago
      I mean, it is definitely a problem. https://pasteboard.co/xzgTi4TxK326.jpg https://pasteboard.co/xzgTi4TxK326.jpg
      - tomcam 4y ago
        SEE I’M NOT INSANE!
robbiemckinstry 4y ago
Am I still correct in saying these two features are still missing from Wasm? 1. Native Strings 2. DOM interaction

dmitriid 4y ago

So it looks like it's basically slapping a 2.0 on standardized features from the roadmap: https://webassembly.org/roadmap/ https://webassembly.org/roadmap/

richdougherty 4y ago
I think that's the process, yes. Features get proposed, discussed, implemented, then eventually when they're done they're moved into the spec and tagged with a version.
- dmitriid 4y ago
  Just realised this will make it easier for tools like caniuse. Instead of listing all features, they can just have "webgpu 2.0 availability"

tomcam 4y ago

Appreciate this. Can you explain why there appear to be English-looking letters used for terms but with alternate Unicode versions? Makes everything look jumbly but I'm sure there's a good reason.

richdougherty 4y ago
Are you talking about the MathJax rendering used for instruction names?
- tomcam 4y ago
  False alarm. I think it's a font rendering problem on Safari. When I tried Chrome and Firefox it didn't appear. For example, under "External Types" at https://www.w3.org/TR/wasm-core-2/syntax/types.html#external-types https://www.w3.org/TR/wasm-core-2/syntax/types.html#external... you see this grammar rule: externtype ::= func functype | table tabletype | mem memtype | global globaltype On Safari, the tokens fun, table, men, and global render with weird font baselines on some letters: c, o, e and a are raised a few points higher than they should be. I just figured these were odd substitutions for ASCII characters from further in the Unicode alphabet, maybe to avoid collisions with other reserved token names or something (vamping here because it was all I could think of). Sorry about that.
  - cormacrelf 4y ago
    I mean, it is definitely a problem. https://pasteboard.co/xzgTi4TxK326.jpg https://pasteboard.co/xzgTi4TxK326.jpg
    - tomcam 4y ago
      SEE I’M NOT INSANE!

robbiemckinstry 4y ago

Am I still correct in saying these two features are still missing from Wasm? 1. Native Strings 2. DOM interaction