nom-derive is a custom derive attribute, to derive nom parsers automatically from the structure definition.
It is not meant to replace nom, but to provide a quick and easy way to generate parsers for structures, especially for simple structures. This crate aims at simplifying common cases. In some cases, writing the parser manually will remain more efficient.
- API documentation
- Documentation of
Nom
attribute. This is the main documentation for this crate, with all possible options and many examples.
Feedback welcome !
This crate exposes a single custom-derive macro Nom
which
implements parse
for the struct it is applied to.
The goal of this project is that:
derive(Nom)
should be enough for you to derive nom parsers for simple structures easily, without having to write it manually- it allows overriding any parsing method by your own
- it allows using generated parsing functions along with handwritten parsers and combining them without efforts
- it remains as fast as nom
nom-derive
adds declarative parsing to nom
. It also allows mixing with
procedural parsing easily, making writing parsers for byte-encoded formats
very easy.
For example:
use nom_derive::Nom;
#[derive(Nom)]
struct S {
a: u32,
b: u16,
c: u16
}
This adds a static method parse
to S
, with the following signature:
impl S {
pub fn parse(i: &[u8]) -> nom::IResult(&[u8], S);
}
To parse input, just call let res = S::parse(input);
.
For extensive documentation of all attributes and examples, see the Nom derive attribute documentation.
Many examples are provided, and more can be found in the project tests.
All inferred parsers will generate code with absolute type path, so there is no need
to add use
statements for them. However, if you use any combinator directly (or in a Parse
statement, for ex.), it has to be imported as usual.
That is probably not going to change, since
- a proc_macro cannot export items other than functions tagged with
#[proc_macro_derive]
- there are variants of combinators with the same names (complete/streaming, bits/bytes), so re-exporting them would create side-effects.
- If the generated parser does not compile, add
#[nom(DebugDerive)]
to the structure. It will dump the generated parser tostderr
. - If the generated parser fails at runtime, try adding
#[nom(Debug)]
to the structure or to fields. It wraps subparsers indbg_dmp
and will print the field name and input tostderr
if the parser fails.
- Add LengthCount attribute (#15)
- Add f32 and f64 as native types (#16)
- Rewrite error handling to raise compile errors (instead of panic)
- Fix build for syn 1.0.58 (#11)
- Upgrade to nom 6
- Add support for guards in Selector Patterns (#5)
- Add limited support for Unit fields in enum (#6)
- Make
parse
method public for enums too (#7)
- Add ExtraArgs support for structs (top-level only)
- Allow dynamic configuration of endianness (SetEndian attribute)
- Add support for
u128
/i128
(#3)
- Add Tag attribute
- Fix type verification with Cond when using multiple attributes
- Switch to nom parsing functions, do not generate macros
- Use qualified paths, caller do not have to import nom macros
- Move all attributes under the 'nom' namespace
- Add many attributes (LittleEndian, BigEndian, Map, Debug, Value, Take, AlignAfter/AlignBefore, SkipAfter/SkipBefore, ErrorIf, etc.)
- Deprecate the
NomDeriveDebug
derive (replaced byDebugDerive
attribute) - Improve documentation, add many examples
- Rewrite attribute parser, now accepting a more flexible syntax
- Upgrade to nom 5.0
- The
parse
method is now public - Upgrade dependencies (syn, quote, proc-macro2)
- Add support for
Enum
parser generator- Enums require a selector to choose the variant
- Fieldless enums (list of constants) are handled as a special case
- Add
NomDeriveDebug
attribute to display generated parser on stderr during build
- Move crate to rust-bakery github project
- Add
Count
attribute
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.