repo stringclasses 1
value | pull_number int64 266 411 | instance_id stringclasses 8
values | issue_numbers sequencelengths 1 1 | base_commit stringclasses 7
values | patch stringclasses 8
values | test_patch stringclasses 8
values | problem_statement stringclasses 8
values | hints_text stringclasses 6
values | created_at stringclasses 8
values | version stringclasses 5
values | FAIL_TO_PASS sequencelengths 1 6 | PASS_TO_PASS sequencelengths 57 81 | FAIL_TO_FAIL sequencelengths 0 0 | PASS_TO_FAIL sequencelengths 0 0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
bitflags/bitflags | 411 | bitflags__bitflags-411 | [
"406"
] | 9c4b93c931e34a5104f50e20be1bdd15bc593b0e | diff --git a/src/lib.rs b/src/lib.rs
index 8f722591..b5e8911b 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -38,7 +38,7 @@ bitflags! {
See the docs for the `bitflags` macro for the full syntax.
-Also see the [`example_generated`] module for an example of what the `bitflags` macro generates for a flags type.
+Also se... | diff --git a/tests/compile-pass/bitflags_impl_attrs.rs b/tests/compile-pass/bitflags_impl_attrs.rs
new file mode 100644
index 00000000..91d89823
--- /dev/null
+++ b/tests/compile-pass/bitflags_impl_attrs.rs
@@ -0,0 +1,13 @@
+extern crate bitflags;
+
+struct Example(u64);
+
+bitflags::bitflags! {
+ /// Docs on the `i... | Allow specifying attributes in `impl` mode
I'm considering `cfg`-gating the use of `bitflags!` in my libraries, and to that end it would be nice if it was possible to apply attributes to the generated `impl`s as well.
The naive solution would be:
```rust
pub struct Flags(u8);
#[cfg(feature = "bitflags")]
bitfl... | Thanks for the report @madsmtm! Anywhere attributes are allowed to be specified we should support in the macros as much as possible. I think this is just a missing piece of functionality for the impl mode. | 2024-06-24T23:17:40Z | 2.5 | [
"tests/compile-pass/bitflags_impl_attrs.rs"
] | [
"tests::complement::cases",
"tests::bits::cases",
"tests::all::cases",
"tests::contains::cases",
"tests::difference::cases",
"tests::empty::cases",
"tests::eq::cases",
"tests::extend::cases",
"tests::extend::external::cases",
"tests::flags::external::cases",
"tests::from_bits::cases",
"tests::... | [] | [] |
bitflags/bitflags | 355 | bitflags__bitflags-355 | [
"357"
] | 31d3e4afefc964045156d7fe3622733f48511353 | diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml
index 6ebd5a74..15d1f950 100644
--- a/.github/workflows/rust.yml
+++ b/.github/workflows/rust.yml
@@ -81,6 +81,23 @@ jobs:
- name: Default features
run: cross test --target mips-unknown-linux-gnu
+ clippy:
+ name: Clippy
+ run... | diff --git a/tests/compile-fail/bitflags_custom_bits.rs b/tests/compile-fail/bitflags_custom_bits.rs
index 46fde469..b719de4f 100644
--- a/tests/compile-fail/bitflags_custom_bits.rs
+++ b/tests/compile-fail/bitflags_custom_bits.rs
@@ -19,7 +19,7 @@ use std::{
},
};
-use bitflags::{bitflags, Bits, parser::{Parse... | Clippy warnings around "manual implementation of an assign operation"
Hi.
I've run into a new clippy lint warnings such as the following:
> manual implementation of an assign operation
> for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#assign_op_pattern
> `#[warn(clippy::a... | 2023-05-17T11:22:15Z | 2.3 | [
"tests/compile-pass/bitflags_self_in_value.rs"
] | [
"tests::bits_types",
"tests::into_iter_from_iter_roundtrip",
"tests::submodule::test_private",
"tests::test_assignment_operators",
"tests::test_binary",
"tests::test_bits",
"tests::test_const_fn",
"tests::test_contains",
"tests::test_debug",
"tests::test_deprecated",
"tests::test_display_from_st... | [] | [] | |
bitflags/bitflags | 351 | bitflags__bitflags-351 | [
"348"
] | 1d8388bf4ce18afde846d220ad8b6e0dc40aae94 | "diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml\nindex a32e1d55..6ebd5a74 1006(...TRUNCATED) | "diff --git a/tests/compile-fail/visibility/private_flags.rs b/tests/compile-fail/access_outside_vis(...TRUNCATED) | "Allow external impls of Bits and BitFlags\nThe `BitFlags` trait is currently sealed, and is only su(...TRUNCATED) | "As for `Bits`, it can be reasonably reduced to:\r\n\r\n```rust\r\npub trait Bits:\r\n Clone\r\n (...TRUNCATED) | 2023-05-04T06:16:51Z | 2.2 | ["tests/compile-pass/bitflags_trait_bound_flags.rs","tests/compile-pass/bitflags_trait_to_flags.rs",(...TRUNCATED) | ["tests::bits_types","tests::submodule::test_private","tests::test_assignment_operators","tests::tes(...TRUNCATED) | [] | [] |
bitflags/bitflags | 345 | bitflags__bitflags-345 | [
"344"
] | cbcafa710fc31172511e62efa06ad9eb214e4734 | "diff --git a/src/example_generated.rs b/src/example_generated.rs\nindex 9c1ba46a..b7589014 100644\n(...TRUNCATED) | "diff --git a/tests/compile-pass/large.rs b/tests/compile-pass/large.rs\nnew file mode 100644\nindex(...TRUNCATED) | "Bitflags reverses order of multiline doc comments\nWhen compiling code like\r\n```\r\nbitflags! {\r(...TRUNCATED) | "This should be trivially fixed by swapping the order attributes are \"pushed\" in `__declare_bitfla(...TRUNCATED) | 2023-04-24T04:29:26Z | 2.2 | [
"tests/compile-pass/large.rs"
] | ["tests::bits_types","tests::into_iter_from_iter_roundtrip","tests::submodule::test_private","tests:(...TRUNCATED) | [] | [] |
bitflags/bitflags | 341 | bitflags__bitflags-341 | [
"308"
] | dc971042c8132a5381ab3e2165983ee7f9d44c63 | "diff --git a/src/lib.rs b/src/lib.rs\nindex 7ba784c5..a4a40467 100644\n--- a/src/lib.rs\n+++ b/src/(...TRUNCATED) | "diff --git a/tests/compile-pass/doc_alias.rs b/tests/compile-pass/doc_alias.rs\nnew file mode 10064(...TRUNCATED) | "Cannot use `#[doc(alias)]`\nThe following code:\r\n```rs\r\nbitflags::bitflags! {\r\n #[doc(alias (...TRUNCATED) | "This is a general problem for attributes that can't be applied to expressions now. In methods like (...TRUNCATED) | 2023-04-18T00:36:26Z | 2.1 | [
"tests/compile-pass/doc_alias.rs"
] | ["tests::bits_types","tests::into_iter_from_iter_roundtrip","tests::submodule::test_private","tests:(...TRUNCATED) | [] | [] |
bitflags/bitflags | 281 | bitflags__bitflags-281 | [
"215"
] | f38ce72d11ef3e264d4b62f360bd8a5597b916d9 | "diff --git a/src/bitflags_trait.rs b/src/bitflags_trait.rs\nindex 0ffee465..440d5274 100644\n--- a/(...TRUNCATED) | "diff --git a/tests/compile-fail/cfg/multi.stderr b/tests/compile-fail/cfg/multi.stderr\ndeleted fil(...TRUNCATED) | "Debug formatting leads to less desireable output\n[Link to rust playground](https://play.rust-lang.(...TRUNCATED) | "I think the current algorithm used for debug output is to loop over all flags and append identifier(...TRUNCATED) | 2022-05-03T06:59:46Z | 1.3 | ["tests/compile-pass/cfg/redefined-value.rs","tests/compile-pass/deprecated.rs","tests/compile-pass/(...TRUNCATED) | ["tests::test_assignment_operators","tests::submodule::test_private","tests::test_binary","tests::te(...TRUNCATED) | [] | [] |
bitflags/bitflags | 268 | bitflags__bitflags-268 | [
"267"
] | 1aa25e1b3baf35d3d3840f12fe7e8b55adc0164a | "diff --git a/src/lib.rs b/src/lib.rs\nindex 617afea0..b24fb40b 100644\n--- a/src/lib.rs\n+++ b/src/(...TRUNCATED) | "diff --git a/tests/compile-fail/trait/custom_impl.rs b/tests/compile-fail/trait/custom_impl.rs\nind(...TRUNCATED) | "Bug: debug pretty-printing unknown flags display 0x0x\nmain.rs\r\n```rust\r\nuse bitflags::bitflags(...TRUNCATED) | 2022-01-02T17:22:14Z | 1.3 | [
"tests/compile-pass/impls/fmt.rs"
] | ["tests::submodule::test_private","tests::test_assignment_operators","tests::test_binary","tests::te(...TRUNCATED) | [] | [] | |
bitflags/bitflags | 266 | bitflags__bitflags-266 | [
"265"
] | 1aa25e1b3baf35d3d3840f12fe7e8b55adc0164a | "diff --git a/src/lib.rs b/src/lib.rs\nindex 617afea0..a4ca8429 100644\n--- a/src/lib.rs\n+++ b/src/(...TRUNCATED) | "diff --git a/tests/compile-pass/redefinition/result.rs b/tests/compile-pass/redefinition/result.rs\(...TRUNCATED) | "The bitflags macro is not sanitary wrt. standard library types and enumerations\nThe `bitflags` mac(...TRUNCATED) | 2021-12-16T09:38:14Z | 1.3 | [
"tests/compile-pass/redefinition/result.rs"
] | ["tests::submodule::test_private","tests::test_assignment_operators","tests::test_binary","tests::te(...TRUNCATED) | [] | [] |
README.md exists but content is empty.
- Downloads last month
- 4