two-bucket: declare compliance with 1.4.0 by changing descriptions #748
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
Note that two-bucket was added to the Rust track at #375 At the time it declared 1.0.0 compliance, but was actually compliant with 1.2.0 already! Further updates to 1.3.0 and 1.4.0 require no action on the Rust track's part. 1.0.1: Fix exercise name exercism/problem-specifications#715 Unversioned(!): Change descriptions exercism/problem-specifications#716 (Our descriptions are no better or worse, so might as well keep them) 1.1.0: Add cases where goal equals one bucket's capacity exercism/problem-specifications#763 Rust already had these cases, so just update the descriptions 1.2.0: Fix a test case added in 1.1.0 exercism/problem-specifications#911 exercism/problem-specifications#941 Rust already had the correct values, so no action. 1.3.0: move inputs to `input` object exercism/problem-specifications#1084 1.4.0: rename JSON keys to camelCase exercism/problem-specifications#1136
petertseng
added
the
sync/tests
coriolinus
approved these changes
Nov 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note that two-bucket was added to the Rust track at
#375
At the time it declared 1.0.0 compliance, but was actually compliant
with 1.2.0 already!
Further updates to 1.3.0 and 1.4.0 require no action on the Rust track's
part.
1.0.1: Fix exercise name
exercism/problem-specifications#715
Unversioned(!): Change descriptions
exercism/problem-specifications#716
(Our descriptions are no better or worse, so might as well keep them)
1.1.0: Add cases where goal equals one bucket's capacity
exercism/problem-specifications#763
Rust already had these cases, so just update the descriptions
1.2.0: Fix a test case added in 1.1.0
exercism/problem-specifications#911
exercism/problem-specifications#941
Rust already had the correct values, so no action.
1.3.0: move inputs to
inputobjectexercism/problem-specifications#1084
1.4.0: rename JSON keys to camelCase
exercism/problem-specifications#1136