Skip to content

gccrs: dont care about the coercion result here - #4920

Open
philberty wants to merge 1 commit into
masterfrom
phil/mismatched
Open

philberty wants to merge 1 commit into
masterfrom
phil/mismatched

Conversation

@philberty

Copy link
Copy Markdown
Member

We dont actually care here because when libcore is involved the resolve operator overload is gonna resolve to the relevant libcore piece and do the coercion there.

Fixes #4913

gcc/rust/ChangeLog:

* typecheck/rust-hir-type-check-expr.cc (TypeCheckExpr::visit): Ignore result.

gcc/testsuite/ChangeLog:

* rust/compile/issues/4913.rs: New test.

We dont actually care here because when libcore is involved the resolve
operator overload is gonna resolve to the relevant libcore piece and
do the coercion there.

Fixes #4913

gcc/rust/ChangeLog:

	* typecheck/rust-hir-type-check-expr.cc (TypeCheckExpr::visit): Ignore result.

gcc/testsuite/ChangeLog:

	* rust/compile/issues/4913.rs: New test.

Signed-off-by: Philip Herron <herron.philip@googlemail.com>
@philberty philberty added the core Issue related to the compilation of the `core` crate label Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issue related to the compilation of the `core` crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mismatched types, expected ‘u64’ but got ‘u32’

1 participant