No string interpolation in show methods
#456
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
Contributor
|
AdvancedHMC.jl documentation for PR #456 is available at: |
ErikQQY
approved these changes
Jun 9, 2025
Collaborator
ErikQQY
left a comment
ErikQQY
left a comment
There was a problem hiding this comment.
LGTM, string interpolations is not good since they introduce overheads.
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.
String interpolation in
showmethods (many instances recently introduced in #446) is unnecessary. The Julia docs even explicitly advise against it: https://docs.julialang.org/en/v1/manual/performance-tips/#Avoid-string-interpolation-for-I/O