Skip to content
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.

Sign up for GitHub

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

Jump to bottom

resolve failure when setting enum discriminator to a declared const #2428

Closed
msullivan opened this issue May 22, 2012 · 3 comments
Closed

resolve failure when setting enum discriminator to a declared const #2428

msullivan opened this issue May 22, 2012 · 3 comments
Labels
A-resolve Area: Name resolution I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Milestone
0.5

Comments

@msullivan
Copy link
Contributor 

const foo: int = 4 >> 1;
enum bs { thing = foo }
fn main() { assert(thing as int == foo); }

fails with

resolve-bug.rs:4:18: 4:21 error: internal error looking up a definition
resolve-bug.rs:4 enum bs { thing = foo }
msullivan added a commit that referenced this issue May 22, 2012
@msullivan
Add a test for Issue #2428.
2a9bf09
@catamorphism
Copy link
Contributor

Test this again when #1935 is completed.

@bstrie
Copy link
Contributor

bstrie commented Jul 16, 2012

Still hitting this error despite new resolve.

@bstrie bstrie mentioned this issue Sep 18, 2012
Closed
@ghost ghost assigned catamorphism Oct 8, 2012
@catamorphism
Copy link
Contributor

I've fixed this, just waiting for the tree to be open again.

bors added a commit to rust-lang-ci/rust that referenced this issue Sep 22, 2022
@bors
Auto merge of rust-lang#2428 - RalfJung:cargo-miri-runner, r=RalfJung
17bb2c0 
cargo-miri: use '--config target.runner' rather than the TARGET_RUNNER env vars

That means we can properly escape spaces in our filename. This should fix rust-lang/miri#2417, hopefully for real this time. We can also specify a "leading command" which makes it much easier to disambiguate runner invocations from rustdoc invocations!

Thanks to `@ehuss` for suggesting this.
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@celinval @zhassan-aws
Limit FFI calls by default to explicitly supported ones (rust-lang#2428)
6e91d13 
C-FFI is fairly unstable right now and the lack of error handling causes a poor experience when things go wrong.

In this PR, we limit its usage to only support CBMC built-in functions that are explicitly included in Kani and alloc functions from kani_lib.c. User's should still be enable to go back to previous behavior by enabling unstable C-FFI support

Co-authored-by: Zyad Hassan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-resolve Area: Name resolution I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Projects
None yet
Milestone
0.5
Development

No branches or pull requests
3 participants
@msullivan @catamorphism @bstrie