Skip to content
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

Tracking Issue for general floating point formatting #69486

Closed
mxxo opened this issue Feb 26, 2020 · 2 comments
Closed

Tracking Issue for general floating point formatting #69486

mxxo opened this issue Feb 26, 2020 · 2 comments
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature.

Comments

@mxxo
Copy link

mxxo commented Feb 26, 2020

This is a tracking issue for general human-readable floating point formatting akin to C's printf("%g").

RFCs:

Link Description
RFC 844 Original request for a %g-style format
RFC 2729 Detailed RFC by @ExpHP proposing a {:g?} Debug formatter following the stabilization of {:x?}.

Open questions:

  1. Format specifier and trait (:g | :g? | :#?). Extend Debug or introduce LowerGen, UpperGen formatting traits?

From RFC 2729:

  1. The precise format is subject to heavy bikeshedding.
  2. When should the format be considered final? On stabilization of {:g?}? On stabilization of {:g} if it occurs?
  3. Public API for this and RFC 2226

Links:

Pre-RFC discussion: https://internals.rust-lang.org/t/pre-rfc-draft-g-or-floating-points-for-humans/9110

Related crates:

@mxxo mxxo added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label Feb 26, 2020
@jonas-schievink
Copy link
Contributor

rust-lang/rfcs#2729 has not been accepted yet

@droudy
Copy link

droudy commented Feb 26, 2020

@droundy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature.
Projects
None yet
Development

No branches or pull requests

3 participants