Skip to content

Add case default#274

Merged
adammaycock merged 2 commits intodevelopfrom
feature/273
Feb 4, 2026
Merged

Add case default#274
adammaycock merged 2 commits intodevelopfrom
feature/273

Conversation

@DJDavies2
Copy link
Collaborator

Resolves #273.

This fix is semantically equivalent to the code in develop. However it is probably not correct as looking at the relative select case blocks it looks like if the select falls through to the end and doesn't match anything it is probably an error and the code should abort. This would be a change of behaviour and it might fail tests. Let me know which you would prefer.

@DJDavies2
Copy link
Collaborator Author

Copy link
Contributor

@stemiglio stemiglio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see your point on the probable need of a fatal error when fields are not found. But as you say this may produce changes in the tests. Perhaps we could at least ad a warning? See my comment below.

Copy link
Contributor

@stemiglio stemiglio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding the warning messages!

@adammaycock adammaycock merged commit 297242b into develop Feb 4, 2026
6 checks passed
@adammaycock adammaycock deleted the feature/273 branch February 4, 2026 07:38
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.

Fortitude: select case blocks without case default

4 participants