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
struct with unknow value from enum in slice variable
I tried this code:
#[repr(C)]#[derive(Copy,Clone)]pubenumIpc{CREAT = 0o0001000,// POSIXNOWAIT = 2048,// POSIX}pubstructMsgBuf{pubmtype:u32,pubmtext:[u8;Ipc::MSG_BUFFasusize],// <- The error is Ipc::MSG_BUFF, this variable not exist.}fnmain(){}
I expected to see this happen:
error: unresolved name `MSG_BUFF`
Instead, this happened:
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: run with `RUST_BACKTRACE=1`for a backtrace
thread 'rustc' panicked at 'path not fully resolved: PathResolution { base_def: DefTy(DefId { krate: 0, node: 4 }Ipc, true), last_private: LastMod(AllPublic), depth: 1 }', ../src/librustc/middle/def.rs:80
playpen: application terminated with error code 101
The text was updated successfully, but these errors were encountered:
adjivas
changed the title
internal compiler error with a unknow value inside a slice
internal compiler error with a unknown value in a slice
Sep 26, 2015
sfackler
added
A-resolve
Area: Name/path resolution done by `rustc_resolve` specifically
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
labels
Sep 26, 2015
The behavior here isn't really ideal, but we can't really do much better
given the current state of constant evaluation.
Fixesrust-lang#28670, and probably a bunch of duplicates.
…=nikomatsakis
The behavior here isn't really ideal, but we can't really do much better
given the current state of constant evaluation.
The changes to ExprUseVisitor are to avoid a compile error; apparently
that bit of code is extremely sensitive to changes in other areas of the
compiler.
Fixesrust-lang#28670, and probably a bunch of duplicates.
…=nikomatsakis
The behavior here isn't really ideal, but we can't really do much better
given the current state of constant evaluation.
The changes to ExprUseVisitor are to avoid a compile error; apparently
that bit of code is extremely sensitive to changes in other areas of the
compiler.
Fixesrust-lang#28670, and probably a bunch of duplicates.
struct with unknow value from enum in slice variable
I tried this code:
I expected to see this happen:
error: unresolved name `MSG_BUFF`
Instead, this happened:
The text was updated successfully, but these errors were encountered: