Skip to content

internal compiler error w/ dominator and wasm #67813

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

Closed
dakom opened this issue Jan 2, 2020 · 6 comments
Closed

internal compiler error w/ dominator and wasm #67813

dakom opened this issue Jan 2, 2020 · 6 comments
Labels
C-bug Category: This is a bug. E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@dakom
Copy link

dakom commented Jan 2, 2020

I am using the dominator crate for wasm. There is very little documentation on the crate (it's early days) and so I accidentally used it the wrong way. Instead of getting the usual type of compiler errors, I got the following:

thread 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: DistinctSources(DistinctSources { begin: (Macros("::dominator::macros::apply_methods"), BytePos(13989417)), end: (Macros("::dominator::macros::with_node"), BytePos(13989825)) })', src\libcore\result.rs:1165:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.40.0-nightly (c23a7aa77 2019-10-19) running on x86_64-pc-windows-msvc

note: compiler flags: -C debuginfo=2 -C incremental --crate-type cdylib

note: some of the compiler flags provided by cargo are hidden

The way I mistakenly tried to use it was like this:

fn get_dom_tree() -> Dom {
    html!("div", {
        .with_node!(element => {
            .new(element)
        })
    })
}
@jonas-schievink jonas-schievink added C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 2, 2020
@jonas-schievink
Copy link
Contributor

The actual error message is missing. Also, can you provide a self-contained repository that reproduces the ICE?

@jonas-schievink jonas-schievink added the E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example label Jan 2, 2020
@dakom
Copy link
Author

dakom commented Jan 2, 2020

whups, edited just now to paste in the error message. will put together a repo now...

@dakom
Copy link
Author

dakom commented Jan 2, 2020

@jonas-schievink
Copy link
Contributor

Thanks, that helps! This looks like a duplicate of #66805. I'll keep it open in case someone finds a minimal code example that reproduces the problem.

@Enselic
Copy link
Member

Enselic commented Aug 22, 2023

Triage: I can't reproduce this, not even with an older nightly. Can anyone of you still reproduce?

@Enselic
Copy link
Member

Enselic commented Oct 12, 2023

Triage: Closing as not reproducible.

@Enselic Enselic closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants