-
-
Notifications
You must be signed in to change notification settings - Fork 170
uefi: Make TimeError more descriptive #1211
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
Conversation
Is there a reason for no top level enums in |
Ah, I see the relevant section in |
LGTM apart from #1211 (review) |
I instead went with the struct method, allowing one to specify multiple errors. Is this |
We're almost there. Just add one more comment and we are good to go |
When returning a TimeError, it'd be helpful to specify to the user which field is invalid so that it can be handled accordingly, or at least communicated. This change does this by adding bool fields to the TimeError struct, representing the validity of each field of a Time struct.
When returning a TimeError, it'd be helpful to specify to the user which field is invalid so that it can be handled accordingly, or at least communicated. This change does this by reimplementing TimeError as an enum instead of a struct, allowing for specification and more verbose error display.
Checklist