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

string parsing followup: introduce better fitting error type + raise MSRV #177

Merged
merged 3 commits into from
Sep 21, 2023

Conversation

phip1611
Copy link
Collaborator

@phip1611 phip1611 commented Sep 21, 2023

This is a follow-up of #172.

A new StringError error type was introduced and the MSRV is bumped from 1.68 to 1.69.

FYI: Ping @A0lson

@phip1611 phip1611 force-pushed the cstring-follow-up branch 2 times, most recently from 1540b64 to 4e23697 Compare September 21, 2023 14:47
@phip1611 phip1611 changed the title string parsing followup: introduce better fitting error type string parsing followup: introduce better fitting error type + raise MSRV Sep 21, 2023
This is required because of the usage of `core::ffi::CStr::from_bytes_until_nul`
This aligns the name with the inner error. In the codebase, however, we use
"null". NUL often refers to the ANSI character `0`/NUL and null or NULL to
a zero pointer, i.e., to nothing. For now, we keep null everywhere except
for the StringError::MissingNul.
@phip1611 phip1611 added this to the multiboot2: v0.19 milestone Sep 21, 2023
@phip1611 phip1611 merged commit d055b41 into main Sep 21, 2023
28 checks passed
@phip1611 phip1611 deleted the cstring-follow-up branch September 21, 2023 15:13
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.

1 participant