Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Tracking issue for release notes of #138879: Ensure non-empty buffers for large vectored I/O #143144

Open
Labels
O-hermitOperating System: Hermit O-unixOperating system: Unix-like T-libsRelevant to the library team, which will review and decide on the PR/issue. T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue. relnotesMarks issues that should be documented in the release notes of the next release. relnotes-tracking-issueMarks issues tracking what text to put in release notes.
@rustbot

Description

This issue tracks the release notes text for #138879.

cc @thaliaarchi, @tgross35 -- original issue/PR authors and assignees for drafting text

See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.

Release notes text

This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:

  • Does this need an additional compat notes section?
  • Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?
# Libraries
- [Ensure non-empty buffers for large vectored I/O](https://github.com/rust-lang/rust/pull/138879)

Tip

Use the previous releases for inspiration on how to write the release notes text and which categories to pick.

Release blog section

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.

Note

If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.

Metadata

Metadata

Assignees

No one assigned

    Labels

    O-hermitOperating System: Hermit O-unixOperating system: Unix-like T-libsRelevant to the library team, which will review and decide on the PR/issue. T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue. relnotesMarks issues that should be documented in the release notes of the next release. relnotes-tracking-issueMarks issues tracking what text to put in release notes.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /