Skip to content

HIR: explain in comment why ExprKind::If "then" is an Expr #141059

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

Conversation

samueltardieu
Copy link
Contributor

One could be tempted to replace the "then" hir::Expr with kind hir::ExprKind::Block by a hir::Block. Explain why this would not be a good idea.

I've been there.

r? @compiler-errors

One could be tempted to replace the "then" `hir::Expr` with kind
`hir::ExprKind::Block` by a `hir::Block`. Explain why this would not be
a good idea.
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels May 15, 2025
@compiler-errors
Copy link
Member

thanks!

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented May 15, 2025

📌 Commit cf878d8 has been approved by compiler-errors

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 15, 2025
hkBst added a commit to hkBst/rust that referenced this pull request May 16, 2025
…=compiler-errors

HIR: explain in comment why `ExprKind::If` "then" is an `Expr`

One could be tempted to replace the "then" `hir::Expr` with kind `hir::ExprKind::Block` by a `hir::Block`. Explain why this would not be a good idea.

I've been there.

r? `@compiler-errors`
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 59ad0cb 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#141059 - samueltardieu:push-trvpulpskwwp, r=compiler-errors

HIR: explain in comment why `ExprKind::If` "then" is an `Expr`

One could be tempted to replace the "then" `hir::Expr` with kind `hir::ExprKind::Block` by a `hir::Block`. Explain why this would not be a good idea.

I've been there.

r? ``@compiler-errors``
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants