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

Optimization using ByteString #24

Open
msakai opened this issue Feb 25, 2020 · 0 comments
Open

Optimization using ByteString #24

msakai opened this issue Feb 25, 2020 · 0 comments

Comments

@msakai
Copy link
Collaborator

msakai commented Feb 25, 2020

I confirmed Geoff Sutcliffe that TPTP files are always in ASCII. (Current TPTP-v7.3.0.tgz contains some files with non-ASCII characters in UTF-8, but he said he will fix them.)

So it might be possible to use ByteString to improve efficiency:

  • read file as lazy ByteString and feed it to Alex directly without going through String (Note that Alex internally uses UTF-8),
  • dump formula into bytestring Builder instead of ShowS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant