-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
add more docs regarding ideographic numbers #99628
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
r? @scottmcm (rust-highfive has picked a reviewer for you, use r? to override) |
The code sample could also be updated to include a few number-like things that aren't detected as numeric. |
2bd70bf
to
8492a49
Compare
I added your suggestion @the8472 and I think your description is really good to put inside the docs, I have no better way to explain it, maybe if there are any suggestions on the form I can apply them. I also add an example of a number, and I'm thinking to add a comment like |
8492a49
to
334ff7d
Compare
Perhaps 一, 二, 三 are more intuitive examples even when one is not familiar with chinese characters. The comment can also be a bit shorter like
|
334ff7d
to
d2dd96a
Compare
Zero knowledge of Chinese so I put a better char example :) thanks |
@vincenzopalazzo already adding an example that clarifies what ideographic number is would be nice. Just change it to "ideographic numbers like '三'". |
d2dd96a
to
d852d7f
Compare
Added also this clarification @est31 thanks! |
@vincenzopalazzo This most recent change seems to have lost the much more detailed version you had before. |
Since it looks like you're already keeping up with this PR and the meeting discussions about the issue, |
f19af32
to
8c33531
Compare
@joshtriplett Thanks to catch this, I think my remote editor was outdate and did not get update with the last version of the again, thanks! |
8c33531
to
87c47a1
Compare
Signed-off-by: Vincenzo Palazzo <[email protected]>
87c47a1
to
47a0a56
Compare
@bors r+ rollup |
Thanks for working on this! |
Rollup of 6 pull requests Successful merges: - rust-lang#99628 (add more docs regarding ideographic numbers) - rust-lang#99689 (Revert `write!` and `writeln!` to late drop temporaries) - rust-lang#99807 (Fix PermissionDenied UI tests on WSL) - rust-lang#99817 (rustdoc: remove Clean trait impls for more items) - rust-lang#99851 (Fix small typo in Cargo.toml comment) - rust-lang#99856 (fix: remove fake no_dead_strip for osx) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…oc, r=joshtriplett docs: remove repetition in `is_numeric` function docs In rust-lang#99628 we introduce new docs for the `is_numeric` function, and this is a follow-up PR that removes some unnecessary repetition that may be introduced by some rebasing. `@rustbot` r? `@joshtriplett`
…htriplett docs: remove repetition in `is_numeric` function docs In rust-lang/rust#99628 we introduce new docs for the `is_numeric` function, and this is a follow-up PR that removes some unnecessary repetition that may be introduced by some rebasing. `@rustbot` r? `@joshtriplett`
This was discussed in the last lib meeting and I try to avoid forgetting to open a PR because I think having some docs can help people.
However, I think we need to discuss a little bit if this is enough or if we need to add more clarification? Maybe an example?
Inspiration Source: #84056 (comment)
Including suggestion #99626 (comment) my bad command git close the PR