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

errors: clarify names of integer types #334

Merged
merged 1 commit into from
May 9, 2022

Conversation

martinvonz
Copy link
Contributor

I got this error message:

invalid type: integer 64 bit `5`, expected an array

It took me a while to figure out that it wasn't talking about bit
number 5 of the number 64, but the 64-bit number 5. I think it will
be clearer like this:

invalid type: 64-bit integer `5`, expected an array

So that's what this patch implements.

@matthiasbeyer
Copy link
Collaborator

Thank you for this PR and especially thank you for taking the time to explain why you did this in the commit message. Highly appreciated!

@matthiasbeyer
Copy link
Collaborator

The CI fail is unrelated, feel free to simply rebase this to latest master and it should be green then 😆

I got this error message:

```
invalid type: integer 64 bit `5`, expected an array
```

It took me a while to figure out that it wasn't talking about bit
number 5 of the number 64, but the 64-bit number `5`. I think it will
be clearer like this:

```
invalid type: 64-bit integer `5`, expected an array
```

So that's what this patch implements.
@martinvonz
Copy link
Contributor Author

The CI fail is unrelated, feel free to simply rebase this to latest master and it should be green then 😆

That's now done.

@matthiasbeyer matthiasbeyer merged commit 2cdf839 into mehcode:master May 9, 2022
YounessBird pushed a commit to YounessBird/config-rs that referenced this pull request Jun 1, 2022
errors: clarify names of integer types

fix yaml to parse int keys
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.

None yet

2 participants