Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there,
this PR exchanges else prongs with explicit types using exhaustive option checks when possible.
It only exchanges where it seemed reasonable to me. So there is still room for more exchanges here like e.g.:
Since the
std.builtin.Type
is a pretty large union the list gets pretty big and i did not like it:While i am more okey with this last one, it also consumes quite an amount of lines plus
zls
always reformats it to the above example ;)Is there something one could do about this? My zig knowledge comes to an end here, in my dreams i would somehow put those values in a const and than use that in the switch. However i was not successful with this.
WDYT? Should the
else
prong stay in the case of a huge list?