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

Use asserts instead of println in Display docstrings #403

Merged

Conversation

sukhmel
Copy link
Contributor

@sukhmel sukhmel commented Jan 20, 2025

I've recently discovered that I was using strum incorrectly assuming that content of variants will be printed. In 0.26 the content can be printed but as this is not the default, I've decided that it may still be beneficial to clarify in the docs what to expect from the default option.

To better convey the results and make sure the user expectations are set right, I propose to use assert_eq + format instead of println as the latter is not very informative without specifying what should be printed as a result.

sukhmel and others added 2 commits January 20, 2025 14:39
To better convey the results and make sure the user expectations are set right, use `assert_eq` + `format` instead of `println` that is not very informative without specifying what should be printed.
@sukhmel
Copy link
Contributor Author

sukhmel commented Jan 29, 2025

I was hasty and missed an incorrect copy-paste. Now everything should pass

@Peternator7 Peternator7 merged commit 043dc12 into Peternator7:master Feb 8, 2025
1 check failed
@Peternator7
Copy link
Owner

Seems reasonable to me 👍

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.

3 participants