Skip to content

Update Rust crate nom to v8#451

Merged
taspelund merged 2 commits intomainfrom
renovate/nom-8.x
Mar 24, 2026
Merged

Update Rust crate nom to v8#451
taspelund merged 2 commits intomainfrom
renovate/nom-8.x

Conversation

@oxide-renovate
Copy link
Copy Markdown
Contributor

@oxide-renovate oxide-renovate Bot commented Mar 23, 2025

This PR contains the following updates:

Package Type Update Change
nom workspace.dependencies major 7.18.0

Release Notes

rust-bakery/nom (nom)

v8.0.0

Compare Source

This version represents a significant refactoring of nom to reduce the amount of code generated by parsers, and reduce the API surface. As such, it comes with some breaking changes, mostly around the move from closure based combinators to trait based ones. In practice, it means that instead of writing combinator(arg)(input), we now write combinator(arg).parse(input).

This release also marks the introduction of the nom-language crate, which will hold tools more focused on language parsing than the rest of nom, like the VerboseError type and the newly added precedence parsing combinators.

Thanks
Added
  • Parser::map_res
  • Parser::map_opt
  • many and fold combinators using ranges
  • many can collect into other types than Vec
  • Error and VerboseError can be converted to owned versions
Removed
  • nom::bits::* is no longer re-exported at the crate root. This export caused frequent confusion, since e.g. nom::complete::tag referred to nom::bits::complete::tag instead of the much more commonly used nom::bytes::complete::tag. To migrate, change any imports of nom::{complete::*, streaming::*, bits, bytes} to nom::bits::[...].
  • parse combinator
  • InputIter, InputTakeAtPosition, InputLength, InputTake and Slice are now merged in the Input trait
Changed
  • Parser::map and Parser::flat_map now take a FnMut as argument

Configuration

📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Los_Angeles, Automerge - "after 8pm,before 6am" in timezone America/Los_Angeles.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@oxide-renovate oxide-renovate Bot force-pushed the renovate/nom-8.x branch from 11f80cc to 3fc83a7 Compare May 12, 2025 06:50
@oxide-renovate oxide-renovate Bot force-pushed the renovate/nom-8.x branch from 3fc83a7 to 4acdf51 Compare June 6, 2025 11:04
@oxide-renovate oxide-renovate Bot force-pushed the renovate/nom-8.x branch 3 times, most recently from 4d4ca84 to 4372480 Compare September 13, 2025 03:06
@oxide-renovate oxide-renovate Bot force-pushed the renovate/nom-8.x branch 3 times, most recently from bd237d2 to 69d8b49 Compare January 8, 2026 04:16
@oxide-renovate oxide-renovate Bot force-pushed the renovate/nom-8.x branch 2 times, most recently from 9b71eb5 to f969688 Compare February 12, 2026 04:30
@oxide-renovate oxide-renovate Bot force-pushed the renovate/nom-8.x branch 2 times, most recently from 068d8c7 to 27f9e99 Compare March 21, 2026 03:26
nom stopped implementing Input for fixed-size arrays, so instead pass a
byte slice.
@oxide-renovate
Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@taspelund taspelund merged commit 0b35ff6 into main Mar 24, 2026
15 checks passed
@taspelund taspelund deleted the renovate/nom-8.x branch March 24, 2026 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant