Update documentation on switch to explain the fallthrough enum case better - #333
Open
regier21 wants to merge 1 commit into
Open
Update documentation on switch to explain the fallthrough enum case better#333regier21 wants to merge 1 commit into
regier21 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I was confused about why an empty case was required in a
switchstatement that covers everyenummember when returning from theswitch. I even opened an issue to that effect in the main Odin repo, but I was told that this was intended behavior to account forenumvariables possibly taking on invalid values. This is unusual compared to other languages I've used and I thought it might trip some other people up, so I added some clarifying info into the overview to explain this.