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.

Sign up for GitHub

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

Jump to bottom

Why are LanguageDef and TokenParser restricted to String streams? #95

Closed
sjakobi opened this issue May 16, 2018 · 1 comment
Closed

Why are LanguageDef and TokenParser restricted to String streams? #95

sjakobi opened this issue May 16, 2018 · 1 comment

Comments

@sjakobi
Copy link
Member

sjakobi commented May 16, 2018

It's not immediately obvious to me why there is this restriction.

In particular, I'd like to use the haskell TokenParser on a Text stream.
@sjakobi sjakobi mentioned this issue May 16, 2018
Open
@sjakobi
Copy link
Member Author

sjakobi commented May 16, 2018

Duplicate of #55.

@sjakobi sjakobi closed this as completed May 16, 2018
int-index pushed a commit to int-index/parsec that referenced this issue Sep 18, 2020
@judah
Simplify and speed up the Travis CI. (haskell#95)
1067a3d 
- Use Travis's build-in apt support
- Use `language: c` explicitly
- Remove unnecessary `cabal` invocations
- Remove the separate `before_install` step
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sjakobi