Allow crate link attributes to contain nested meta items #607
Comments
ghost
assigned 
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
Add x86_64 module to uclibc/mod.rs
pdietl
pushed a commit
to pdietl/rust
that referenced
this issue
Apr 23, 2020
Specify behavior of int->float and f64->f32 casts
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 26, 2020
Bumps [miniz-sys](https://github.com/alexcrichton/flate2-rs) from 0.1.11 to 0.1.12. - [Release notes](https://github.com/alexcrichton/flate2-rs/releases) - [Commits](rust-lang/flate2-rs@miniz-sys-0.1.11...miniz-sys-0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
ZuseZ4
added a commit
to EnzymeAD/rust
that referenced
this issue
Mar 7, 2023
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
…-lang#657) * Introduce rmc::any and rmc::any_raw and deprecate rmc::nondet We decided to replace the old method rmc::nondet because its behavior wasn't clear. For some types it would respect the type invariants but not for others. Additionally, there was no way for the user to specify how to create safe non-deterministic values. Users will be able to control how RMC generate symbolic values to their variables. - `rmc::any::<T>()` will provide a safe way to generate values that respect any invariant specified to type T (Given by the implementation of Arbitrary trait.) - `rmc::any_raw::<T>()` will provide any possible bit value for the memory layout of the type. This is an unsafe method and users must ensure correctness after this call. Co-authored-by: Zyad Hassan <88045115+zhassan-aws@users.noreply.github.com> Co-authored-by: Adrian Palacios <73246657+adpaco-aws@users.noreply.github.com>
GuillaumeGomez
pushed a commit
to GuillaumeGomez/rust
that referenced
this issue
Jan 24, 2025
Remove extra whitespace at the end of some line strings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's currently impossible to define a link attribute that has nested meta items,
#[link(foo(bar))];, even though this is a valid way to write an attribute. There are unfinished branches in two methods, link::build_link_meta (that prevents translation), and attr::eq (that prevents the attribute from being matched in a use statement), that need to be filled in.Unfortunately it's not possible to formulate a test case for this within the current test framework, so instead of writing potentially broken code, I've just made these scenarios fail.
The text was updated successfully, but these errors were encountered: