Tracking WebAssembly features

[petamoriken]

WebAssembly features implemented in browsers is unknown. Fortunately, the WebAssembly feature detection library is available and it can be tracked.

FYI: WebAssembly/proposals#21

[gsnedders]

The biggest part of this is we need to decide how to model many of these extensions (i.e., what granularity we want… do we want to have a compat entry for each instruction? or do we want to group these by high-level extensions like "threads"?).

[MendyBerger]

@gsnedders think tracking high level extensions makes the most sense, browsers have for the most part been adding whole new extensions at once, not instruction by instruction.
In the case where a browser does add only parts of an extension it can be marked with partial_implementation.

Thoughts?

[MendyBerger]

@queengooborg what do you think? (I was told that you're the one that can make a decision here)

Feel free to assign to me if you agree with my previous comment.

[queengooborg]

This sounds great and would certainly be a big help in keeping BCD auto-maintained! Perhaps this is something we can integrate into the collector project? https://github.com/GooborgStudios/mdn-bcd-collector

[MendyBerger]

@queengooborg I'd be happy to look into that