Skip to content

Navigation Menu

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

Appearance settings

Add #[must_use] to Array::map #140957

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

Merged
merged 1 commit into from
May 17, 2025
Merged

Conversation

JulianKnodt
Copy link
Contributor

The output of Array::map is intended to be an array of the same size, and does not modify the original in place nor is it intended for side-effects. Thus, under normal circumstances it should be consumed.

See discussion.

Attaching to tracking issue #75243

@rustbot
Copy link
Collaborator

rustbot commented May 13, 2025

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels May 13, 2025
@rust-log-analyzer

This comment has been minimized.

The output of Array::map is intended to be an array of the same size, and does not modify the
original in place nor is it intended for side-effects. Thus, under normal circumstances it should be consumed.

See [discussion](https://internals.rust-lang.org/t/array-map-annotate-with-must-use/22813/26).

Attaching to tracking issue rust-lang#75243
@Mark-Simulacrum Mark-Simulacrum added the relnotes Marks issues that should be documented in the release notes of the next release. label May 16, 2025
@Mark-Simulacrum
Copy link
Member

@bors r+

This seems reasonable.

@bors
Copy link
Collaborator

bors commented May 16, 2025

📌 Commit ab1c49a has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 16, 2025
@scottmcm
Copy link
Member

@bors rollup

bors added a commit to rust-lang-ci/rust that referenced this pull request May 17, 2025
…iaskrgr

Rollup of 8 pull requests

Successful merges:

 - rust-lang#140208 (Make well-formedness predicates no longer coinductive)
 - rust-lang#140957 (Add `#[must_use]` to Array::map)
 - rust-lang#141031 (Async drop fix for dropee from another crate (rust-lang#140858))
 - rust-lang#141036 (ci: split the dist-ohos job)
 - rust-lang#141051 (Remove some unnecessary erases)
 - rust-lang#141056 (Lowercase git url for rust-lang/enzyme.git)
 - rust-lang#141059 (HIR: explain in comment why `ExprKind::If` "then" is an `Expr`)
 - rust-lang#141070 (Do not emit help when shorthand from macro when suggest `?` or `expect`)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 642cd65 into rust-lang:master May 17, 2025
6 checks passed
@rustbot rustbot added this to the 1.89.0 milestone May 17, 2025
rust-timer added a commit to rust-lang-ci/rust that referenced this pull request May 17, 2025
Rollup merge of rust-lang#140957 - JulianKnodt:array_must_use, r=Mark-Simulacrum

Add `#[must_use]` to Array::map

The output of Array::map is intended to be an array of the same size, and does not modify the original in place nor is it intended for side-effects. Thus, under normal circumstances it should be consumed.

See [discussion](https://internals.rust-lang.org/t/array-map-annotate-with-must-use/22813/26).

Attaching to tracking issue rust-lang#75243
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relnotes Marks issues that should be documented in the release notes of the next release. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.