Skip to content

Conversation

@matthewmcgarvey
Copy link
Member

Fixes #1118

This fixes a compilation error where an operation is made with a need that has a default value and there are needs defined after it without a default. I'm not sure if it matters, but OPERATION_NEEDS will be in a different order now. All needs without a default value will be in the reverse order they were defined and at the front of the list, and needs with a default value will be in the order they were defined but at the end of the list. If the ordering needs to be maintained, everywhere that uses the list in the needy initializer files will need to sort it first.

Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

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

oh sweet! Thanks for fixing that 🥳

@matthewmcgarvey matthewmcgarvey merged commit 1e02bc7 into main Dec 22, 2025
8 checks passed
@matthewmcgarvey matthewmcgarvey deleted the mm/1118 branch December 22, 2025 15:56
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.

Order of needs shouldn't matter with default values

3 participants