Add flower-field, deprecating minesweeper
#989
Merged
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
BNAndras
force-pushed
the
add-flower-field
branch
from
a1b694e to
97c11c5
Compare
BNAndras
force-pushed
the
add-flower-field
branch
from
ce8bc31 to
ce52e85
Compare
Contributor
|
@BNAndras thank you for this! Would you mind if I used the chance to make a few minor improvements to the examplary implementation and then merge? |
Member
Author
|
Sure, feel free. I just borrowed the minesweeper example solution so it doesn’t matter to me. |
ahans
approved these changes
Jul 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://forum.exercism.org/t/suggestion-deprecate-minesweeper-for-flower-field/17967