[hist] Always use maximum floating point precision in GetExpFormula
#19734
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.
In #18194, an optional parameter to
TFormula::GetExpFormula()
was introduced, which can be used to customize the precision when putting parameters into the jitted code.However, I don't see the reason why wouldn't like to always print the floating point numbers with maximum precision, which is suggested in this commit.
This is achieved using modern C++ functions, which are also not respecting the users locale setting, but instead use the classic C locale by default, which is what we need when generating code.
Follows up on #18194 (and its partial revert #18216).
Closes #17225.
Replaces #17327.