kelbon

Also your godbolt link looks like gcc bug

> So I'm pretty sure at this point that I've hit a codegen bug with WASM, and it's a nightmare to reduce so I'm gonna have to shelve for now....

Its `feed`

> Local results > > ``` > Parse /home/grisumbras/dev/boost/libs/json/bench/data/apache_builds.json,gcc x64/sse2,boost (direct),363 > Parse /home/grisumbras/dev/boost/libs/json/bench/data/apache_builds.json,gcc x64/sse2,boost (pool),369 > Parse /home/grisumbras/dev/boost/libs/json/bench/data/apache_builds.json,gcc x64/sse2,glaze,1381 > > Parse /home/grisumbras/dev/boost/libs/json/bench/data/canada.json,gcc x64/sse2,boost (direct),496 > Parse /home/grisumbras/dev/boost/libs/json/bench/data/canada.json,gcc x64/sse2,boost...

> Can you give a link? If it doesn't break parse_into API, I may integrate it into the library myself. First of all, i see you use only gcc in...

> that's because of our fallback command logic, it assumes `.h` files are of language objectivec++ to provide most coverage, which breaks such macros. This will be broken in many...

@314eter will this pr be merged? I agree with @OctarineDragon in https://github.com/summerwind/h2spec/issues/78, test requires incorrect behavior