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
SiegeLord opened this issue
Oct 20, 2013
· 1 comment
Labels
A-linkageArea: linking into static, shared libraries and binariesI-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
test.rc:(.text+0x3d): undefined reference to `internal::core::Struct::init::h168b469d58ae6141v5a1::v0.0'
test.o: In function `internal::core::Trait::test::h265f5d5a4f11b6da2::v0.0':
test.rc:(.text+0xf5): undefined reference to `internal::core::private::he344781a19bc4532aJ::v0.0'
The text was updated successfully, but these errors were encountered:
This is another case of reachability not propagating public-ness through the re-exported traits. This may be something that middle::privacy needs to take into account. I will think about this.
A-linkageArea: linking into static, shared libraries and binariesI-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
I found two more cases when a pub use of a private item results in link-time errors.
lib.rs
test.rs
commands:
Current output:
The text was updated successfully, but these errors were encountered: