print floating point values at full precision by default #14339
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
Comments
|
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#796 |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 20, 2023
fix: don't replace `SyntaxToken` with `SyntaxNode` Fixes rust-lang#14339 When we inline method calls, we replace the `self` parameter with a local variable `this`. We have been replacing the `self` **tokens** with `NameRef` **nodes**, which makes the AST malformed. This leads to crash when we apply path transformation after the replacement (which only takes place when the method is generic and such scenario was not tested).
flip1995
added a commit
to flip1995/rust
that referenced
this issue
Mar 20, 2025
This PR: - lints more case of raw pointer comparisons - do not omit the named function to raw pointer conversion before suggesting - trigger the `ptr_eq` lint only if `cmp_null` doesn't trigger first, as this is a more specialized version - lints against `!=` in addition to `==` The `ptr_eq` code has been moved from under `operators` to `ptr.rs`, in order to benefit from factorization. Fix rust-lang#14337 changelog: [`ptr_eq`]: handle more cases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By rounding to a specific number of digits by default, the standard library is causing confusion. Printing to a specified precision is very useful, but it should only happen via
{:.2}rather than by default.The text was updated successfully, but these errors were encountered: