Skip to content

custom-set: remove Debug trait bound from stub#889

Merged
coriolinus merged 1 commit intoexercism:masterfrom
coriolinus:fix-631
Oct 13, 2019
Merged

custom-set: remove Debug trait bound from stub#889
coriolinus merged 1 commit intoexercism:masterfrom
coriolinus:fix-631

Conversation

@coriolinus
Copy link
Copy Markdown
Member

Closes #631.

Closes exercism#631.

Retain Debug derive so assert_eq works.
Copy link
Copy Markdown
Member

@petertseng petertseng left a comment

Choose a reason for hiding this comment

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

While I don't think it was necessary to remove the unimplemented messages entirely, I don't object, on the basis that these functions are hopefully self-explanatory...

The alternative I was thinking of would be to use an unimplemented message that doesn't mention the element. Such as Determine if the element is present in the set.

I pre-emptively approve as I would be satisfied with any choice made, but feel free to ask if the messages and changed and I should take a look at the messages.

@coriolinus
Copy link
Copy Markdown
Member Author

IMO the descriptive messages aren't adding much; in my view, they're a hack to use the variable more than useful text on their own. That's why I removed them here.

@coriolinus coriolinus merged commit ff7b403 into exercism:master Oct 13, 2019
@coriolinus coriolinus deleted the fix-631 branch October 13, 2019 07:43
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.

What trait bounds are appropriate for stubs?

2 participants