repo string | pull_number int64 | instance_id string | issue_numbers list | base_commit string | patch string | test_patch string | problem_statement string | hints_text string | created_at string | version string | updated_at string | environment_setup_commit string | FAIL_TO_PASS list | PASS_TO_PASS list | FAIL_TO_FAIL list | PASS_TO_FAIL list | source_dir string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
rinja-rs/askama | 788 | rinja-rs__askama-788 | [
"786"
] | 417cb924ae1f94d54e2eb13ebc7e9fab91b84588 | diff --git a/askama_derive/src/generator.rs b/askama_derive/src/generator.rs
--- a/askama_derive/src/generator.rs
+++ b/askama_derive/src/generator.rs
@@ -630,16 +630,16 @@ impl<'a> Generator<'a> {
self.write_let(buf, ws, var, val)?;
}
Node::Cond(ref conds, ws) => ... | diff --git /dev/null b/testing/templates/size-child-super.txt
new file mode 100644
--- /dev/null
+++ b/testing/templates/size-child-super.txt
@@ -0,0 +1,2 @@
+{% extends "size-parent.txt" %}
+{% block main %}{% call super() %}{% endblock %}
diff --git /dev/null b/testing/templates/size-child.txt
new file mode 100644
--... | Is write_cond trying to return a size_hint?
It looks like `write_cond` is accumulating a contribution to `size_hint`:
https://github.com/djc/askama/blob/417cb924ae1f94d54e2eb13ebc7e9fab91b84588/askama_derive/src/generator.rs#L760
But it seems to be dropped on the floor:
https://github.com/djc/askama/blob/417cb924a... | Same question for `write_match`, `write_loop`, `write_block`, maybe others? I'm starting to think there's more to accumulating the `size_hint` than it looks like at first glance? | 2023-03-06T20:45:26Z | 0.12 | 2023-03-07T09:53:22Z | 4dab5f91ba15e7c238ddf6223ec7b45eef32cab4 | [
"test_block_size_hint",
"test_loop_size_hint",
"test_cond_size_hint",
"test_match_size_hint",
"test_super_size_hint"
] | [] | [] | [] | auto_2025-06-03 |
rinja-rs/askama | 436 | rinja-rs__askama-436 | [
"435"
] | 000aff4a18c90a5074afd1af5587ff94e915e7d1 | diff --git a/askama_escape/src/lib.rs b/askama_escape/src/lib.rs
--- a/askama_escape/src/lib.rs
+++ b/askama_escape/src/lib.rs
@@ -88,7 +93,7 @@ where
escaper: E,
}
-impl<'a, E> ::std::fmt::Display for Escaped<'a, E>
+impl<'a, E> Display for Escaped<'a, E>
where
E: Escaper,
{
| diff --git a/askama_escape/src/lib.rs b/askama_escape/src/lib.rs
--- a/askama_escape/src/lib.rs
+++ b/askama_escape/src/lib.rs
@@ -1,5 +1,10 @@
-use std::fmt::{self, Display, Formatter, Write};
-use std::str;
+#![no_std]
+
+#[cfg(test)]
+extern crate std;
+
+use core::fmt::{self, Display, Formatter, Write};
+use core::... | no-std support for askama_escape
Just taking a glance through the code, nothing that required `std` popped out to me, if you're happy to make this crate no-std compatible I can prepare a PR for it?
| 2021-01-15T22:04:25Z | 0.10 | 2021-01-15T22:35:34Z | 49252d2457f280026c020d0df46733578eb959a5 | [
"tests::test_escape"
] | [] | [] | [] | auto_2025-06-03 | |
rinja-rs/askama | 1,027 | rinja-rs__askama-1027 | [
"1026"
] | 8d3a3f73d4b06c4bfe7417bb4cee3b6c49c1a5fc | diff --git a/askama_parser/src/node.rs b/askama_parser/src/node.rs
--- a/askama_parser/src/node.rs
+++ b/askama_parser/src/node.rs
@@ -2,7 +2,7 @@ use std::borrow::Cow;
use std::str;
use nom::branch::alt;
-use nom::bytes::complete::{tag, take_until};
+use nom::bytes::complete::tag;
use nom::character::complete::ch... | diff --git a/askama_parser/src/tests.rs b/askama_parser/src/tests.rs
--- a/askama_parser/src/tests.rs
+++ b/askama_parser/src/tests.rs
@@ -918,3 +918,17 @@ fn fuzzed_unary_recursion() {
const TEMPLATE: &str = include_str!("../tests/unary-recursion.txt");
assert!(Ast::from_str(TEMPLATE, None, &Syntax::default(... | Nested comments causes parser to timeout
Hi,
Large nested comments like below(produced by fuzzing);
```
{{#{{#{{#{{#{{#{{#{{#{{#{{#{{#{{#{{#{{#{{#{{##}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#}#
```
makes the parser get stuck at following lines.
https://github.com/djc/askama/blob/5955ba23c172ef6bbc0116b9ab0d6f0... | 2024-04-30T21:00:38Z | 0.13 | 2024-05-01T11:55:08Z | 53b4b518f9a230665029560df038c318b2e55458 | [
"tests::fuzzed_comment_depth"
] | [
"test::test_num_lit",
"test::test_char_lit",
"tests::change_delimiters_parse_filter",
"tests::fuzzed_macro_no_end",
"tests::fuzzed_unicode_slice",
"tests::test_invalid_block - should panic",
"tests::test_missing_space_after_kw",
"tests::test_associativity",
"tests::test_parse_const",
"tests::test_... | [
"test::test_strip_common"
] | [] | auto_2025-06-03 | |
axodotdev/cargo-dist | 1,135 | axodotdev__cargo-dist-1135 | [
"36"
] | ff3d2ba9b0f0a25bb64dbf8d31e865fb32b9a2f1 | diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -126,24 +126,6 @@ version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c4b4d0bd25bd0b74681c0ad21497610ce1b7c91b1022cd21c80c6fbdd9476b0"
-[[package]]
-name = "axoasset"
-version = "0.9.5"
-source = "r... | diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -62,17 +62,17 @@ jobs:
# Make sure the docs build without warnings
docs:
- runs-on: ubuntu-latest
- env:
- RUSTDOCFLAGS: -Dwarnings
- steps:
- - uses: actions/checkout@... | handle colliding targets properly
Under the current design, we:
1. Compute everything that needs to be done
2. Build all targets that need to be built
3. Copy artifacts from builds.
4. Bundle
I believe this will do the wrong thing if you told cargo-dist that you want builds that differ only in feature flags. i... | Also note that this bug can't be witnessed right now because we have no way to pass in build settings :) | 2024-06-17T16:55:16Z | 4.5 | 2024-06-17T18:58:14Z | ff3d2ba9b0f0a25bb64dbf8d31e865fb32b9a2f1 | [
"backend::installer::homebrew::tests::class_caps_after_numbers",
"backend::installer::homebrew::tests::ends_with_dash",
"backend::installer::homebrew::tests::ampersand_but_no_digit",
"backend::installer::homebrew::tests::handles_dashes",
"backend::installer::homebrew::tests::class_case_basic",
"backend::i... | [] | [] | [] | auto_2025-06-11 |
biomejs/biome | 585 | biomejs__biome-585 | [
"44"
] | 8287c1a37bc7024ce4f9c88f32d7dd96678c51aa | diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -96,6 +96,13 @@ Read our [guidelines for writing a good changelog entry](https://github.com/biom
- Fix [#591](https://github.com/biomejs/biome/issues/591) which made [noRedeclare](https://biomejs.dev/linter/rules/no-redeclare) report typ... | diff --git /dev/null b/crates/biome_js_analyze/src/analyzers/nursery/no_unused_private_class_members.rs
new file mode 100644
--- /dev/null
+++ b/crates/biome_js_analyze/src/analyzers/nursery/no_unused_private_class_members.rs
@@ -0,0 +1,365 @@
+use biome_analyze::{
+ context::RuleContext, declare_rule, ActionCategor... | 📎 Implement `lint/noUnusedPrivateClassMembers` - `eslint/no-unused-private-class-members`
### Description
[no-unused-private-class-members](https://eslint.org/docs/latest/rules/no-unused-private-class-members/)
**Want to contribute?** Lets you know you are interested! We will assign you to the issue to prevent s... | @Conaclos I'll work on this one.
This rule should also cover private members in typescript ? or only es2022 class private members ?
I'd say both, because we can :)
Not sure, because private TypeScript field are not ensured to leak. I mean:
```ts
class A {
private n: number;
}
declare const a: A;
const... | 2023-10-23T02:41:54Z | 0.2 | 2023-12-06T21:53:41Z | cf9a586d69b09437bf4b7f075df0aa627daa891d | [
"specs::nursery::no_unused_private_class_members::valid_js",
"specs::nursery::no_unused_private_class_members::invalid_ts",
"specs::nursery::no_unused_private_class_members::invalid_js"
] | [
"analyzers::correctness::no_nonoctal_decimal_escape::tests::test_is_octal_escape_sequence",
"analyzers::correctness::no_nonoctal_decimal_escape::tests::test_get_unicode_escape",
"analyzers::correctness::no_nonoctal_decimal_escape::tests::test_parse_escape_sequences",
"analyzers::suspicious::no_control_charact... | [] | [] | auto_2025-06-09 |
biomejs/biome | 4,791 | biomejs__biome-4791 | [
"3969"
] | 3c32a66294c817d733c9f65c1916328a42c5efa9 | diff --git a/Cargo.toml b/Cargo.toml
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -13,6 +13,7 @@ unused_lifetimes = "warn"
unused_macro_rules = "warn"
[workspace.lints.clippy]
+allow_attributes = "deny"
cargo_common_metadata = "allow"
empty_docs = "allow" # ... | diff --git a/crates/biome_cli/tests/commands/format.rs b/crates/biome_cli/tests/commands/format.rs
--- a/crates/biome_cli/tests/commands/format.rs
+++ b/crates/biome_cli/tests/commands/format.rs
@@ -180,14 +180,10 @@ const APPLY_ATTRIBUTE_POSITION_AFTER: &str = r#"<Foo
</Foo>;
"#;
-// Without this, Test (windows-la... | 📎 Replace Clippy `allow` with `expect`
### Description
Rust 1.81 stabilizes Clippy's [`expect` attribute](https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html#expectlint). This attribute ensures that a lint diagnostic is emitted where the attribute appears.
We should replace `allow` attribute with `expect`.
... | I just noticed you don't use 1.81.0 yet, so this task needs to wait until to move to 1.81
> so this task needs to wait until to move to 1.81
Done in #3972 | 2024-12-24T19:28:20Z | 0.5 | 2024-12-29T16:48:49Z | 2425ce767fc6a93bbd091a5a9ec18beb5476e204 | [
"err::multidigit_number_then_00_json",
"err::structure_null_byte_outside_string_json"
] | [
"commands::tests::incompatible_arguments",
"commands::tests::no_fix",
"diagnostics::test::termination_diagnostic_size",
"execute::migrate::eslint::tests::eslint_package_resolve_name",
"commands::tests::safe_fixes",
"commands::tests::safe_and_unsafe_fixes",
"execute::migrate::ignorefile::tests::negated_p... | [
"commands::explain::explain_help"
] | [
"cases::diagnostics::max_diagnostics_are_lifted",
"commands::lsp_proxy::lsp_proxy_help"
] | auto_2025-06-09 |
boa-dev/boa | 629 | boa-dev__boa-629 | [
"610"
] | ad162e09e39818862c10bcfc08bc788c44a85d5d | diff --git a/boa/src/builtins/string/mod.rs b/boa/src/builtins/string/mod.rs
--- a/boa/src/builtins/string/mod.rs
+++ b/boa/src/builtins/string/mod.rs
@@ -468,7 +468,10 @@ impl String {
let regex_body = Self::get_regex_string(args.get(0).expect("Value needed"));
let re = Regex::new(®ex_body).expe... | diff --git a/boa/src/builtins/string/tests.rs b/boa/src/builtins/string/tests.rs
--- a/boa/src/builtins/string/tests.rs
+++ b/boa/src/builtins/string/tests.rs
@@ -218,6 +218,74 @@ fn replace() {
assert_eq!(forward(&mut engine, "a"), "\"2bc\"");
}
+#[test]
+fn replace_no_match() {
+ let realm = Realm::create(... | Error in RegExp
Hi,
The following code snippet works incorrectly for RegExp
```js
let re = /(\w+)\s(\w+)/
let str = 'John Smith'
let newstr = str.replace(re, '$2, $1')
console.log(newstr)
```
Expected: `Smith, John`
Got: `Smith, $1`
thanks
| Hmmm. This this is probably a bug in `String.prototype.replace`.
I think I've found the mistake and the fix, I'll open a PR soon. | 2020-08-13T21:49:23Z | 0.9 | 2020-09-01T16:41:49Z | 8816df8f434e3ae4ba6f56fb7c49211ec370b916 | [
"builtins::bigint::tests::r#mod"
] | [
"builtins::date::tests::date_display",
"src/builtins/bigint/operations.rs - builtins::bigint::operations::BigInt::mod_floor (line 24)",
"src/builtins/value/mod.rs - builtins::value::Value::display (line 643)"
] | [] | [] | auto_2025-06-09 |
bevyengine/bevy | 15,281 | bevyengine__bevy-15281 | [
"6370",
"6581"
] | 0fe33c3bbaf58ce89d85e97092fc45438d2da4ff | diff --git a/Cargo.toml b/Cargo.toml
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -48,6 +48,10 @@ ref_as_ptr = "warn"
# see: https://github.com/bevyengine/bevy/pull/15375#issuecomment-2366966219
too_long_first_doc_paragraph = "allow"
+std_instead_of_core = "warn"
+std_instead_of_alloc = "warn"
+alloc_instead_of_core = "war... | diff --git a/crates/bevy_app/src/app.rs b/crates/bevy_app/src/app.rs
--- a/crates/bevy_app/src/app.rs
+++ b/crates/bevy_app/src/app.rs
@@ -1116,7 +1115,8 @@ impl Termination for AppExit {
#[cfg(test)]
mod tests {
- use std::{iter, marker::PhantomData, sync::Mutex};
+ use core::{iter, marker::PhantomData};
+ ... | Prefer `core` and `alloc` over `std` where possible
## What problem does this solve or what need does it fill?
Some less common platforms (e.g. Nintendo Switch, and likely other consoles), do not support the full Rust standard library.
Bevy uses a number of features from the standard library, but it's unclear exact... | I would add a O-Console label here, but we don't have one yet :P
Real fast attempt applying this just to bevy_transform and bevy_time, found some quick blockers.
- `std::borrow::Cow` only exists in std, no `core` equivalent exists
- The lints fire on the `PartialEq` macro without `no_std` enabled
`Cow` seems to b... | 2024-09-18T05:48:37Z | 1.81 | 2024-10-20T14:34:22Z | 60b2c7ce7755a49381c5265021ff175d3624218c | [
"app::tests::can_add_two_plugins",
"plugin_group::tests::readd",
"plugin_group::tests::add_basic_subgroup",
"app::tests::events_should_be_updated_once_per_update",
"app::tests::can_add_twice_the_same_plugin_not_unique",
"app::tests::regression_test_10385",
"app::tests::cant_add_twice_the_same_plugin - s... | [
"bounding::bounded2d::aabb2d_tests::area",
"bounding::bounded2d::aabb2d_tests::closest_point",
"bounding::bounded2d::aabb2d_tests::center",
"bounding::bounded2d::aabb2d_tests::contains",
"bounding::bounded2d::aabb2d_tests::grow",
"bounding::bounded2d::aabb2d_tests::half_size",
"bounding::bounded2d::aabb... | [] | [] | auto_2025-06-08 |
dtolnay/async-trait | 260 | dtolnay__async-trait-260 | [
"259"
] | 62969d525fbd76abec15edf00289ced049b7fa0a | diff --git a/src/expand.rs b/src/expand.rs
--- a/src/expand.rs
+++ b/src/expand.rs
@@ -125,6 +125,7 @@ pub fn expand(input: &mut Item, is_local: bool) {
fn lint_suppress_with_body() -> Attribute {
parse_quote! {
#[allow(
+ unused_qualifications,
clippy::async_yields_async,
... | diff --git a/tests/test.rs b/tests/test.rs
--- a/tests/test.rs
+++ b/tests/test.rs
@@ -2,7 +2,7 @@
async_trait_nightly_testing,
feature(impl_trait_in_assoc_type, min_specialization)
)]
-#![deny(rust_2021_compatibility)]
+#![deny(rust_2021_compatibility, unused_qualifications)]
#![allow(
clippy::incompa... | Using async-trait with nightly-2024-03-04 triggers `unused-qualifications` lint
Consider the following code:
```rust
use async_trait::async_trait; // async-trait = "0.1.77"
#[async_trait]
pub trait Foo {
async fn foo(&self);
}
pub struct Bar;
#[async_trait]
impl Foo for Bar {
async fn foo(&se... | 2024-03-16T23:27:55Z | 0.1 | 2024-03-16T23:37:31Z | f8e5bb43181450a17068f160e8a51d410ede1705 | [
"drop_order::test_drop_order",
"issue57::test",
"issue45::tracing",
"issue199::test",
"src/lib.rs - (line 15) - compile fail",
"src/lib.rs - (line 178) - compile fail",
"src/lib.rs - (line 199)",
"src/lib.rs - (line 224)",
"src/lib.rs - (line 141)",
"src/lib.rs - (line 63)",
"src/lib.rs - (line ... | [] | [] | [] | auto_2025-06-06 | |
dtolnay/async-trait | 239 | dtolnay__async-trait-239 | [
"238"
] | 7937a8900b6546dc1c9b2e931647d3d21c854cd0 | diff --git a/src/expand.rs b/src/expand.rs
--- a/src/expand.rs
+++ b/src/expand.rs
@@ -80,13 +80,6 @@ pub fn expand(input: &mut Item, is_local: bool) {
}
}
Item::Impl(input) => {
- let mut lifetimes = CollectLifetimes::new("'impl");
- lifetimes.visit_type_mut(&mut *i... | diff --git a/tests/test.rs b/tests/test.rs
--- a/tests/test.rs
+++ b/tests/test.rs
@@ -1585,3 +1585,22 @@ pub mod issue236 {
}
}
}
+
+// https://github.com/dtolnay/async-trait/issues/238
+pub mod issue238 {
+ #![deny(single_use_lifetimes)]
+
+ use async_trait::async_trait;
+
+ #[async_trait]
+ ... | Weird interaction with `single_use_lifetimes`
[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a3f95d64d1d61fac41ec315a644ae353)
```
warning: lifetime parameter `'impl0` only used once
--> src/lib.rs:7:19
|
7 | impl<T> Trait for &T {}
| ^
| ... | 2023-03-04T06:54:09Z | 0.1 | 2023-03-04T06:56:03Z | f8e5bb43181450a17068f160e8a51d410ede1705 | [
"drop_order::test_drop_order",
"issue199::test",
"issue45::tracing",
"src/lib.rs - (line 15) - compile fail",
"src/lib.rs - (line 165) - compile fail",
"src/lib.rs - (line 286)",
"src/lib.rs - (line 126)",
"src/lib.rs - (line 265)",
"src/lib.rs - (line 211)",
"src/lib.rs - (line 186)",
"src/lib.... | [] | [] | [] | auto_2025-06-06 | |
dtolnay/async-trait | 235 | dtolnay__async-trait-235 | [
"234"
] | 125917ffe0833c07e736e9b048951358d6ada8bb | diff --git a/src/expand.rs b/src/expand.rs
--- a/src/expand.rs
+++ b/src/expand.rs
@@ -403,7 +403,10 @@ fn transform_block(context: Context, sig: &mut Signature, block: &mut Block) {
} else {
quote! {
#(#attrs)*
- let ... | diff --git a/tests/test.rs b/tests/test.rs
--- a/tests/test.rs
+++ b/tests/test.rs
@@ -2,6 +2,7 @@
async_trait_nightly_testing,
feature(min_specialization, type_alias_impl_trait)
)]
+#![deny(rust_2021_compatibility)]
#![allow(
clippy::let_unit_value,
clippy::missing_panics_doc,
diff --git a/tests/... | Nested `_` and `..` patterns under 2018 edition can trigger rust_2021_compatibility warning
The code generated by async-trait should never exhibit edition sensitive behavior differences. The fact that async-trait involves the use of move closures internally is an implementation detail. If the behavior is sensitive to e... | 2023-01-22T21:52:47Z | 0.1 | 2023-01-22T21:54:15Z | f8e5bb43181450a17068f160e8a51d410ede1705 | [
"drop_order::test_drop_order",
"issue199::test",
"issue45::tracing",
"src/lib.rs - (line 15) - compile fail",
"src/lib.rs - (line 165) - compile fail",
"src/lib.rs - (line 286)",
"src/lib.rs - (line 47)",
"src/lib.rs - (line 126)",
"src/lib.rs - (line 186)",
"src/lib.rs - (line 211)",
"src/lib.r... | [] | [] | [] | auto_2025-06-06 | |
tokio-rs/axum | 2,014 | tokio-rs__axum-2014 | [
"2004"
] | 652d65aabce95d508bbf1ee7bf05053c83f0d230 | diff --git a/axum-macros/src/debug_handler.rs b/axum-macros/src/debug_handler.rs
--- a/axum-macros/src/debug_handler.rs
+++ b/axum-macros/src/debug_handler.rs
@@ -263,6 +263,7 @@ fn check_inputs_impls_from_request(item_fn: &ItemFn, state_ty: Type) -> TokenStr
quote_spanned! {span=>
#[all... | diff --git /dev/null b/axum-macros/tests/debug_handler/pass/deny_unreachable_code.rs
new file mode 100644
--- /dev/null
+++ b/axum-macros/tests/debug_handler/pass/deny_unreachable_code.rs
@@ -0,0 +1,8 @@
+#![deny(unreachable_code)]
+
+use axum::extract::Path;
+
+#[axum_macros::debug_handler]
+async fn handler(Path(_): ... | debug_handler macro is incompatible with use of #![deny(unreachable_code)]
<!--
Thank you for reporting an issue.
Please fill in as much of the template below as you're able.
-->
- [x] I have looked for existing issues (including closed) about this
## Bug Report
### Version
<!--
List the versions of a... | Thanks for the report! Should just be a matter of adding `#[allow(unreachable_code)]` to the generated functions. | 2023-05-19T21:30:41Z | 0.6 | 2023-06-24T14:20:49Z | c100650464e96cc9b48a37290760f288d6311ed8 | [
"tests/debug_handler/pass/deny_unreachable_code.rs [should pass]",
"debug_handler::ui",
"tests/from_request/pass/empty_named_parts.rs [should pass]"
] | [
"tests/from_ref/fail/generics.rs [should fail to compile]",
"tests/from_ref/pass/basic.rs [should pass]",
"tests/from_ref/pass/reference-types.rs [should pass]",
"tests/from_ref/pass/skip.rs [should pass]",
"from_ref::ui",
"tests/typed_path/fail/missing_capture.rs [should fail to compile]",
"tests/typed... | [] | [] | auto_2025-06-06 |
tokio-rs/axum | 1,676 | tokio-rs__axum-1676 | [
"1674"
] | 949da2b3002f9568a86f9e2eddec34056ad858db | diff --git a/axum-macros/src/from_ref.rs b/axum-macros/src/from_ref.rs
--- a/axum-macros/src/from_ref.rs
+++ b/axum-macros/src/from_ref.rs
@@ -3,7 +3,7 @@ use quote::quote_spanned;
use syn::{
parse::{Parse, ParseStream},
spanned::Spanned,
- Field, ItemStruct, Token,
+ Field, ItemStruct, Token, Type,
}... | diff --git /dev/null b/axum-macros/tests/from_ref/pass/reference-types.rs
new file mode 100644
--- /dev/null
+++ b/axum-macros/tests/from_ref/pass/reference-types.rs
@@ -0,0 +1,10 @@
+#![deny(noop_method_call)]
+
+use axum_macros::FromRef;
+
+#[derive(FromRef)]
+struct State {
+ inner: &'static str,
+}
+
+fn main() ... | Rustc and clippy warnings generated by derive(FromRef)
<!--
Thank you for reporting an issue.
Please fill in as much of the template below as you're able.
-->
- [X] I have looked for existing issues (including closed) about this
## Bug Report
### Version
<!--
List the versions of all `axum` crates you... | 2023-01-03T21:16:56Z | 0.6 | 2023-01-05T17:51:07Z | c100650464e96cc9b48a37290760f288d6311ed8 | [
"tests/from_request/pass/enum_via.rs [should pass]",
"tests/from_ref/pass/reference-types.rs",
"from_ref::ui"
] | [
"tests/from_request/fail/double_via_attr.rs [should fail to compile]",
"tests/from_request/fail/enum_from_request_ident_in_variant.rs [should fail to compile]",
"tests/from_request/fail/enum_from_request_on_variant.rs [should fail to compile]",
"tests/from_request/fail/enum_no_via.rs [should fail to compile]"... | [] | [] | auto_2025-06-06 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.