Why does nom expect a &str when I pass a CompleteStr?
up vote
0
down vote
favorite
The parser works as expected until I want to parse the h:
digit which is always the last digit in the string and the compiler gives me
^ expected &str, found struct `nom::types::CompleteStr`
I assume it's because the parser is looking ahead. How do I stop that, or how can I signify it's done?
#[macro_use]
extern crate nom;
use nom::digit;
use nom::types::CompleteStr;
use std::str::FromStr;
#[derive(Debug, PartialEq)]
pub struct Order {
pub l: u64,
pub w: u64,
pub h: u64,
}
named!(order_parser<CompleteStr, Order>,
do_parse!(
l: map_res!(digit, u64::from_str) >>
tag!("x") >>
w: map_res!(digit, u64::from_str) >>
tag!("x") >>
h: map_res!(digit, u64::from_str) >>
(Order {l: l, w: w, h: h })
)
);
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<&str>> {
order_parser(order)
}
#[test]
fn test_order_parser() {
assert_eq!(
wrap_order(CompleteStr("2x3x4")),
Ok((CompleteStr(""), Order { l: 2, w: 3, h: 4 }))
);
}
rust nom
add a comment |
up vote
0
down vote
favorite
The parser works as expected until I want to parse the h:
digit which is always the last digit in the string and the compiler gives me
^ expected &str, found struct `nom::types::CompleteStr`
I assume it's because the parser is looking ahead. How do I stop that, or how can I signify it's done?
#[macro_use]
extern crate nom;
use nom::digit;
use nom::types::CompleteStr;
use std::str::FromStr;
#[derive(Debug, PartialEq)]
pub struct Order {
pub l: u64,
pub w: u64,
pub h: u64,
}
named!(order_parser<CompleteStr, Order>,
do_parse!(
l: map_res!(digit, u64::from_str) >>
tag!("x") >>
w: map_res!(digit, u64::from_str) >>
tag!("x") >>
h: map_res!(digit, u64::from_str) >>
(Order {l: l, w: w, h: h })
)
);
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<&str>> {
order_parser(order)
}
#[test]
fn test_order_parser() {
assert_eq!(
wrap_order(CompleteStr("2x3x4")),
Ok((CompleteStr(""), Order { l: 2, w: 3, h: 4 }))
);
}
rust nom
1
I believe your question is answered by the answers of Why does my nom parser not consume the entire input, leaving the last piece unparsed? / Parsing an integer with nom. If you disagree, please edit your question to explain the differences. Otherwise, we can mark this question as already answered.
– Shepmaster
Nov 20 at 2:48
I changed it as I read up and still can't seem to get it to work
– Pumphouse
Nov 20 at 4:29
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The parser works as expected until I want to parse the h:
digit which is always the last digit in the string and the compiler gives me
^ expected &str, found struct `nom::types::CompleteStr`
I assume it's because the parser is looking ahead. How do I stop that, or how can I signify it's done?
#[macro_use]
extern crate nom;
use nom::digit;
use nom::types::CompleteStr;
use std::str::FromStr;
#[derive(Debug, PartialEq)]
pub struct Order {
pub l: u64,
pub w: u64,
pub h: u64,
}
named!(order_parser<CompleteStr, Order>,
do_parse!(
l: map_res!(digit, u64::from_str) >>
tag!("x") >>
w: map_res!(digit, u64::from_str) >>
tag!("x") >>
h: map_res!(digit, u64::from_str) >>
(Order {l: l, w: w, h: h })
)
);
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<&str>> {
order_parser(order)
}
#[test]
fn test_order_parser() {
assert_eq!(
wrap_order(CompleteStr("2x3x4")),
Ok((CompleteStr(""), Order { l: 2, w: 3, h: 4 }))
);
}
rust nom
The parser works as expected until I want to parse the h:
digit which is always the last digit in the string and the compiler gives me
^ expected &str, found struct `nom::types::CompleteStr`
I assume it's because the parser is looking ahead. How do I stop that, or how can I signify it's done?
#[macro_use]
extern crate nom;
use nom::digit;
use nom::types::CompleteStr;
use std::str::FromStr;
#[derive(Debug, PartialEq)]
pub struct Order {
pub l: u64,
pub w: u64,
pub h: u64,
}
named!(order_parser<CompleteStr, Order>,
do_parse!(
l: map_res!(digit, u64::from_str) >>
tag!("x") >>
w: map_res!(digit, u64::from_str) >>
tag!("x") >>
h: map_res!(digit, u64::from_str) >>
(Order {l: l, w: w, h: h })
)
);
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<&str>> {
order_parser(order)
}
#[test]
fn test_order_parser() {
assert_eq!(
wrap_order(CompleteStr("2x3x4")),
Ok((CompleteStr(""), Order { l: 2, w: 3, h: 4 }))
);
}
rust nom
rust nom
edited Nov 20 at 15:50
Shepmaster
145k11274408
145k11274408
asked Nov 20 at 1:22
Pumphouse
1,1861022
1,1861022
1
I believe your question is answered by the answers of Why does my nom parser not consume the entire input, leaving the last piece unparsed? / Parsing an integer with nom. If you disagree, please edit your question to explain the differences. Otherwise, we can mark this question as already answered.
– Shepmaster
Nov 20 at 2:48
I changed it as I read up and still can't seem to get it to work
– Pumphouse
Nov 20 at 4:29
add a comment |
1
I believe your question is answered by the answers of Why does my nom parser not consume the entire input, leaving the last piece unparsed? / Parsing an integer with nom. If you disagree, please edit your question to explain the differences. Otherwise, we can mark this question as already answered.
– Shepmaster
Nov 20 at 2:48
I changed it as I read up and still can't seem to get it to work
– Pumphouse
Nov 20 at 4:29
1
1
I believe your question is answered by the answers of Why does my nom parser not consume the entire input, leaving the last piece unparsed? / Parsing an integer with nom. If you disagree, please edit your question to explain the differences. Otherwise, we can mark this question as already answered.
– Shepmaster
Nov 20 at 2:48
I believe your question is answered by the answers of Why does my nom parser not consume the entire input, leaving the last piece unparsed? / Parsing an integer with nom. If you disagree, please edit your question to explain the differences. Otherwise, we can mark this question as already answered.
– Shepmaster
Nov 20 at 2:48
I changed it as I read up and still can't seem to get it to work
– Pumphouse
Nov 20 at 4:29
I changed it as I read up and still can't seem to get it to work
– Pumphouse
Nov 20 at 4:29
add a comment |
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
The error is not on the last digit parser, it's on each of them (Rust 1.30.0 prints the error three times). That's because u64::from_str
works on &str
, not CompleteStr
.
You can fix your parsers to use u64::from_str
correctly this way:
do_parse!(
l: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
w: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
h: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
(Order { l: l, w: w, h: h })
)
There are also some unrelated error with the next function, which can be fixed by using the appropriate types in the signature:
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<CompleteStr>> {
order_parser(CompleteStr(order))
}
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
The error is not on the last digit parser, it's on each of them (Rust 1.30.0 prints the error three times). That's because u64::from_str
works on &str
, not CompleteStr
.
You can fix your parsers to use u64::from_str
correctly this way:
do_parse!(
l: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
w: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
h: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
(Order { l: l, w: w, h: h })
)
There are also some unrelated error with the next function, which can be fixed by using the appropriate types in the signature:
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<CompleteStr>> {
order_parser(CompleteStr(order))
}
add a comment |
up vote
4
down vote
accepted
The error is not on the last digit parser, it's on each of them (Rust 1.30.0 prints the error three times). That's because u64::from_str
works on &str
, not CompleteStr
.
You can fix your parsers to use u64::from_str
correctly this way:
do_parse!(
l: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
w: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
h: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
(Order { l: l, w: w, h: h })
)
There are also some unrelated error with the next function, which can be fixed by using the appropriate types in the signature:
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<CompleteStr>> {
order_parser(CompleteStr(order))
}
add a comment |
up vote
4
down vote
accepted
up vote
4
down vote
accepted
The error is not on the last digit parser, it's on each of them (Rust 1.30.0 prints the error three times). That's because u64::from_str
works on &str
, not CompleteStr
.
You can fix your parsers to use u64::from_str
correctly this way:
do_parse!(
l: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
w: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
h: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
(Order { l: l, w: w, h: h })
)
There are also some unrelated error with the next function, which can be fixed by using the appropriate types in the signature:
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<CompleteStr>> {
order_parser(CompleteStr(order))
}
The error is not on the last digit parser, it's on each of them (Rust 1.30.0 prints the error three times). That's because u64::from_str
works on &str
, not CompleteStr
.
You can fix your parsers to use u64::from_str
correctly this way:
do_parse!(
l: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
w: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
tag!("x") >>
h: map_res!(digit, |CompleteStr(s)| u64::from_str(s)) >>
(Order { l: l, w: w, h: h })
)
There are also some unrelated error with the next function, which can be fixed by using the appropriate types in the signature:
pub fn wrap_order(order: &str) -> Result<(CompleteStr, Order), nom::Err<CompleteStr>> {
order_parser(CompleteStr(order))
}
edited Nov 21 at 18:52
answered Nov 20 at 8:31
Valentin Lorentz
6,57053355
6,57053355
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384920%2fwhy-does-nom-expect-a-str-when-i-pass-a-completestr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I believe your question is answered by the answers of Why does my nom parser not consume the entire input, leaving the last piece unparsed? / Parsing an integer with nom. If you disagree, please edit your question to explain the differences. Otherwise, we can mark this question as already answered.
– Shepmaster
Nov 20 at 2:48
I changed it as I read up and still can't seem to get it to work
– Pumphouse
Nov 20 at 4:29