Hacker News Reader

Comment by Laaas | Hacker News Reader

Is it just me or does it seem nonsensical that TH splices are compiled to WASM then executed with a WASM interpreter rather than just being interpreted natively by GHC like done with GHCi? Would also fix the weird situation with running git inside splices not working.

View on HN

In general, you must run TH on the target platform for it to be correct. Otherwise, you may generate code that only works on your host (it isn't impossible for TH output to be platform-specific especially since it can do IO)

Well, now the standard can change so it always runs as WASM, and completely fix the issue.

But sometimes it might want to run on the host still (e.g. there are tools out there that generate C bindings that use platform-specific things like sizes and alignments)

If we had pure TH, then at least that could run in wasm. That would be nice.

But idk - I cross-compile Haskell heavily in my free time and I don't mind the external interpreter stuff.

> If we had pure TH, then at least that could run in wasm. That would be nice.

IMO, ideally, pure TH wold be completely platform independent. But running in a standardized VM is a close second place.

Anyway, I never realized those bidings were created with TH.

`inline-c` is the main example I can think of

Yes it's quite an unfortunate situation.

Edward Z Yang has a canonical post on this: http://blog.ezyang.com/2016/07/what-template-haskell-gets-wr...

Reply on news.ycombinator.com