Although the parser is rather easy to use to export Text from Data.Text, the Text.Parsec.Token library is rather hard to use to create a lexer using Text.
I'm not exactly sure how to make the change as of yet -- I'd love to be guided into making the change -- but it would be wonderful if we could somehow parameterize either makeTokenParser or emptyDef so that it would be easier to create a lexer that can handle to the Text type rather than the String from Prelude.
I would love for someone to correct me if I'm wrong and this is doable with the current libary, but at the same time I feel that it could potentially be a reason someone might look somewhere else. Perhaps having an easy way of creating a Text consuming lexer could be a boon to Parsec.
Although the parser is rather easy to use to export
Text
fromData.Text
, theText.Parsec.Token
library is rather hard to use to create a lexer usingText
.I'm not exactly sure how to make the change as of yet -- I'd love to be guided into making the change -- but it would be wonderful if we could somehow parameterize either
makeTokenParser
oremptyDef
so that it would be easier to create a lexer that can handle to theText
type rather than theString
fromPrelude
.I would love for someone to correct me if I'm wrong and this is doable with the current libary, but at the same time I feel that it could potentially be a reason someone might look somewhere else. Perhaps having an easy way of creating a
Text
consuming lexer could be a boon toParsec
.