Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not work with GHCJS #5

Open
andrewthad opened this issue Aug 21, 2018 · 1 comment
Open

Does not work with GHCJS #5

andrewthad opened this issue Aug 21, 2018 · 1 comment

Comments

@andrewthad
Copy link

This does not work with GHCJS because of it uses the c ffi. Not sure if there's a great workaround for this.

@hvr
Copy link
Collaborator

hvr commented Oct 16, 2018

What I'm struggling with is coming up with an answer on whether it makes sense for JavaScript targets to represent strings as UTF8 encoded ByteArray#s or whether it's more efficient to instead use JS' native String objects to represent strings (but which due to historical reasons and lack of foresight are stuck w/ an UTF-16 encoding for the foreseeable future), as JS engines are heavily optimized for that.

The answer to this question decides between two quite different paths...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants