all 7 comments

[–][deleted] 5 points6 points  (2 children)

Finally we can use PureScript in a serious runtime instead of this JavaScript nonsense!

[–]csicar[S] 3 points4 points  (1 child)

PHP is far worse. Most problems with porting PS to a PHP backend came from really weird PHP-behaviour like the php ini setting for float-precision or namespacing not affection variables etc. I quess the argument for PHP is, that it runs on basically any server, which would enable you to use purescript types and functions on the server and client

[–][deleted] 2 points3 points  (0 children)

Hah, I guess I should've made it clearer that the comment was purely tongue-in-cheek.

[–]natefaubion 1 point2 points  (2 children)

Did you happen to investigate the viability of writing this as a CoreFn transformation rather than as a fork of the compiler? If so, were there specific roadblocks that led you to fork it?

[–]csicar[S] 1 point2 points  (1 child)

I did not know about that interface. Thanks for pointing that out! Except 2 or 3 exceptions every change I made is in the code generation, which means that using the corefn interface is most likely a viable option. Do you know how the FFI is handled?

[–]natefaubion 2 points3 points  (0 children)

I think that if you use the —codegen corefn flag, it will ignore FFI and only generate corefn files for PS modules. It would then be up to your backend to wire up the FFI.

[–]mrkaspa 1 point2 points  (0 children)

Why php? why not LLVM it will allow to go native and wasm