Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bracket-push: renamed to matching-brackets #607

Closed
petertseng opened this issue Apr 22, 2019 · 1 comment
Closed

bracket-push: renamed to matching-brackets #607

petertseng opened this issue Apr 22, 2019 · 1 comment

Comments

@petertseng
Copy link
Member

In exercism/problem-specifications#1501, bracket-push was renamed to matching-brackets in problem-specifications, therefore it is recommended that this track (which has the bracket-push exercise) also renames it.

The reasons for this recommendation:

  • to name the exercise by its story, not by what it potentially teaches
  • to avoid unnecessarily biasing the solution space

If this track decides to follow this recommendation, here are some things that may need a change:

  • config.json
  • name of the directory
  • README (contains the name of the exercise)
  • code

If you're not sure what needs to change, feel free to examine PRs to other tracks by looking at any PRs linked to exercism/problem-specifications#1501.

If this track instead decides that accepting this recommendation is a bad idea for the track, then this issue should be closed upon making that decision, and none of the above steps should be taken.

ricemery added a commit to ricemery/xscala that referenced this issue Apr 25, 2019
ricemery added a commit to ricemery/xscala that referenced this issue Apr 25, 2019
ricemery added a commit to ricemery/xscala that referenced this issue Apr 25, 2019
ErikSchierboom pushed a commit that referenced this issue Apr 25, 2019
* Rename bracket-push exercise to matching-brackets.
Refs #607

* Remove unneeded build.properties. Refs #607

* Put pending annotations back in test cases. Refs #607
@petertseng
Copy link
Member Author

apparently I forgot to say "this issue should be closed when the rename is complete"...

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

No branches or pull requests

1 participant