Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork131
Remove deprecation diagnostic supppression for dtostrf#212
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecov-commenter commentedSep 9, 2023
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@## master #212 +/- ##==========================================- Coverage 95.52% 95.50% -0.03%========================================== Files 16 15 -1 Lines 1072 1067 -5 ==========================================- Hits 1024 1019 -5 Misses 48 48 ☔ View full report in Codecov by Sentry. |
robertlipe commentedJul 18, 2025
I'm not a maintainer. This is just a fly-by comment. Isn't thishttps://en.cppreference.com/w/cpp/string/basic_string/to_string.html Adding new names for things that have been in the standard library for years just splits developer mindshare and increases maintenance burden. to_chars, unlike the warning in the code here, doesn't have the risk of buffer overruns. |
Have the tests use an implementation of
dtostrf
which checks for the largest buffer needed by the String class.Document the risks of that implementaton and add a TODO not to rely on this function in the production code.
As this no longer uses the deprecated sample implementation, the warning suppression can be removed as it is not compiled.