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.
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
Fix number implementations are never used #24
Fix number implementations are never used #24
Changes from 4 commits
81136f8
4feed2b
658bbbb
0474e80
539e745
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I'll make this as clear as I can explain with my limited English.
The marked trait (line 96) is defining functions for
str
andString
where usage would be"{Zero}".format(&vars)
.By adding a legacy function here named
strfmt_display
it would make sense to add a similar extension to allow a usage like"{Zero}".format_display(&vars)
as either the original signature would change fromformat<K, D: fmt::Display>(&self, vars: &HashMap<K, D>) -> Result<String>
toformat<K, D: DisplayStr>(&self, vars: &HashMap<K, D>) -> Result<String>
or the body would change and default to use the legacy code.Don't hesitate to ask, sometimes I think way too complicated and by reading these lines I wrote I'm not sure if it gets clear what problem ist the cause for this..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying. I agree with you, there should be two functioned defined by
Format
: