You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rid_build is currently broken. The error message indicates a bug within the Rust tooling:
...
Compiling rid_macro_impl v0.1.0 (https://github.com/thlorenz/rid.git#00126f05)
thread 'rustc' panicked at 'assertion failed: sentinel == STR_SENTINEL', /rustc/0b42deaccc2cbe17a68067aa5fdb76104369e1fd\compiler\rustc_serialize\src\opaque.rs:669:9
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/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: rustc 1.59.0-nightly (0b42deacc 2021-12-09) running on x86_64-pc-windows-msvc
note: compiler flags: -C embed-bitcode=no -C debuginfo=2 --crate-type lib
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
end of query stack
error: could not compile `rid_macro_impl`
warning: build failed, waiting for other jobs to finish...
error: build failed
', rid_build.rs:41:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\rid_build.exe rid_build` (exit code: 101)
This breaks my dev environment in a way that can't be fixed without digging into rid, if only to lock the nightly version.
Is there a workaround for issues with nightly, aside from cloning the repo and locally locking the nightly version? If not, is it possible to move rid away from nightly in the future?
The text was updated successfully, but these errors were encountered:
rid_build
is currently broken. The error message indicates a bug within the Rust tooling:This breaks my dev environment in a way that can't be fixed without digging into rid, if only to lock the nightly version.
Is there a workaround for issues with nightly, aside from cloning the repo and locally locking the nightly version? If not, is it possible to move rid away from nightly in the future?
The text was updated successfully, but these errors were encountered: