Don't re-export private/unstable ArgumentV1 from alloc.

[m-ou-se]

The alloc::fmt::ArgumentV1 re-export was marked as #[stable] even though the original core::fmt::ArgumentV1 is #[unstable] (and #[doc(hidden)]).

(It wasn't usable though:

error[E0658]: use of unstable library feature 'fmt_internals': internal to format_args!
 --> src/main.rs:4:12
  |
4 |     let _: alloc::fmt::ArgumentV1 = todo!();
  |            ^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: add `#![feature(fmt_internals)]` to the crate attributes to enable

)

Part of #99012

[rust-highfive]

r? @thomcc

(rust-highfive has picked a reviewer for you, use r? to override)

[thomcc]

Looks good, r=me once CI passes (looks like it either needs reformatting or a tidy bless)

[Dylan-DPC]

@bors r=thomcc

[bors]

📌 Commit fdc6d1ade8a137e11a4de603a29de238964bbdcf has been approved by thomcc

It is now in the queue for this repository.

[bors]

⌛ Testing commit fdc6d1ade8a137e11a4de603a29de238964bbdcf with merge dad3e742eec65f900b36f21e3951760858bbd1de...

[bors]

💔 Test failed - checks-actions

[thomcc]

@rustbot author

[bors]

☔ The latest upstream changes (presumably #105667) made this pull request unmergeable. Please resolve the merge conflicts.

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout alloc-no-rexport-argumentv1 (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self alloc-no-rexport-argumentv1 --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

CONFLICT (modify/delete): src/test/ui/fmt/ifmt-unimpl.stderr deleted in HEAD and modified in heads/homu-tmp. Version heads/homu-tmp of src/test/ui/fmt/ifmt-unimpl.stderr left in tree.
Auto-merging library/alloc/src/fmt.rs
warning: inexact rename detection was skipped due to too many files.
warning: you may want to set your merge.renamelimit variable to at least 27552 and retry the command.
Automatic merge failed; fix conflicts and then commit the result.

[m-ou-se]

@bors r=thomcc

[bors]

📌 Commit 47adb65 has been approved by thomcc

It is now in the queue for this repository.