Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix misleading error message on UnexpectedType #264

Merged
merged 1 commit into from
Feb 12, 2024

Conversation

Ten0
Copy link
Contributor

@Ten0 Ten0 commented Feb 8, 2024

It's currently named "Unexpected litteral type", but it can also be instantiated when not parsing a litteral, e.g.

pub fn unexpected_expr_type(expr: &Expr) -> Self {

This specifically made investigation of #263 more difficult.

It's currently named "Unexpected litteral type", but it can also be instantiated when not parsing a litteral, e.g. https://github.com/TedDriggs/darling/blob/224a866727cd9e40c2cd80430852b1ea0deeb40e/core/src/error/mod.rs#L152
This specifically made investigation of TedDriggs#263 more difficult.
@TedDriggs TedDriggs merged commit fbcc1b4 into TedDriggs:master Feb 12, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants