megaparsec-6.0.0 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:
versions updated.
Entirely redundant with the above, but do also note:
hspec-megaparsec-1.0.0 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:
My parser seems to break when doing a naive move to v6. It will take me a while to find out why.
Some porting notes, perhaps better here than on reddit:
added where needed:
import Text.Megaparsec.Char
replaced Dec with MPErr and added:
-- build with old or new megaparsec
#if MIN_VERSION_megaparsec(6,0,0)
type MPErr = ErrorFancy Void
#else
type MPErr = Dec
#endif
added these as Text.Megaparsec.String/Text.Megaparsec.Text seem to have gone away:
type SimpleStringParser = Parsec MPErr String
type SimpleTextParser = Parsec MPErr Text
The library itself recommends setting the error type (where MPErr is used above) to Void if its not needed.
Here's a Text.Megaparsec.Compat module, useful for supporting megaparsec <6 and >=6.
@bartavelle If you have any trouble switching please open an issue, I'll help.
@fosskers: this was unfortunate, but I removed "versions" from the build plan since it could not satisfy both the new version of base (which we are upgrading to now) and the old version of Megaparsec (which we are upgrading later).
@mrkkrp I'll try to pinpoint the problem next week. The only meaningful change I did was changing an integer into a decimal, but this gave really weird results (change in whitespace handling, 0x800 parsed as 0). I am sure I did something wrong, so will do that when I have plenty of time to do it properly.
@DanBurton but I bumped my base upper bound too... :(
Hmm... actually I don't think I can support any megaparsecs less than 6 now, since a user requested that I expose some of the internal parsers that versions uses in case they wanted to include version number parsers in a larger parser of their own. Exposing these puts a bit of a stranglehold on versions' major version and dep ranges.
Updated:
hspec-megaparsecstachecue-sheet@mrkkrp Turned out my parser had bugs, but they did not surface with megaparsec 5!
released language-puppet-1.3.9
Fixed for dotenv in version 0.4.0.0
inflections-hs updated! inflections-0.4.0.0 in hackage
Can we perhaps update the checkboxes in the first post?
Checkboxes updated
@mihaimaruseac inflections and dotenv-hs are already updated. Could you please give check our packages in the todo? or are we missing something else?
I see they are updated already.
Yeah. I see they are already checked. Thanks! @mihaimaruseac
I would love to see megaparsec updated to 6.1.1 in stackage-nightly. It looks like many packages are currently on hold for nightly waiting for the others to make the megaparsec update. As time goes on, this seems less fair ;-)
You are right! and I am sorry for being the laggard here. I updated the hledger packages early but have been hung up on the release process. I will release them today.
@simonmichael totally cool: will get them right back as soon as the releases have been made. Thanks!
Thanks @cdornan.
Megaparsec-6 has been blocked for 4 weeks so we have decided to (temporarily we hope) evict the remaining blockers and restore them as soon as they are compatible with megaparsec-6.
I have raised issue in the three projects concerned:
Now that Megaparsec 6 is in nightly builds, can we allow newest stache (1.1.1)?
Most helpful comment
@mihaimaruseac
inflectionsanddotenv-hsare already updated. Could you please give check our packages in the todo? or are we missing something else?