You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
@epage what is the advantage of winnow over nom? I'll need to see what is breaking when it comes to updating the nom dependency as well.
Is there a migration guide for using winnow? I have no particular reason why I'm using one parser combinator library over another, so if either is an easier path to pursue, I'll go in that direction.
https://epage.github.io/blog/2023/02/winnow-toml-edit-combine-nom/#winnow discusses the differences from nom (and the rest covers motivation). Currently, the main advantage is readability improvements but I'm working towards improving handling and performance of more complex text processing cases, like error recovery.
Is there a migration guide for using winnow? I have no particular reason why I'm using one parser combinator library over another, so if either is an easier path to pursue, I'll go in that direction.
Upgrade to nom v7
Switch the dependency and imports to winnow v0.3 (very few changes needed, if any)
Resolve deprecations
Upgrade to winnow 0.4
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
vimwiki appears to use an older version of
nom
that has a future-incompat warning. I see this when building cobalt.If open to alternatives to
nom
, I can offer my biased opinion that winnow is greatThe text was updated successfully, but these errors were encountered: