Source spans lost in strategies when using property_test attribute macro

[zopsicle]

[dev-dependencies.proptest]
version = "1.9.0"
features = ["attr-macro"]

#[property_test]
fn f(#[strategy = 1i32 .. 50i32] a: u32)
{
}

error[E0271]: type mismatch resolving `<RangeInclusive<i32> as Strategy>::Value == u32`
  --> example.rs:1:1
  |
1 |     #[property_test]
  |     ^^^^^^^^^^^^^^^^ expected `u32`, found `i32`
  |

The compiler diagnostic points at the property_test attribute, but should point to strategy or at least the parameter whose type is incorrect, otherwise it is not clear which of the parameters are ill-typed.

[cameron1024]

Hmm, I'm struggling to repro this. Using this code:

#[proptest::property_test]
fn foo(#[strategy = 0..100u32] _x: i32) {}

I get this from cargo test:

error[E0308]: mismatched types
 --> src/main.rs:4:32
  |
4 | fn foo(#[strategy = 0..100u32] _x: i32) {}
  |                                ^^ expected `i32`, found `u32`
  |
help: you can convert a `u32` to an `i32` and panic if the converted value doesn't fit
  |
4 | fn foo(#[strategy = 0..100u32] _x: _x.try_into().unwrap(): i32) {}
  |                                +++   ++++++++++++++++++++

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` (bin "playground" test) due to 1 previous error

I also get similar from rust-analyzer (i.e. the diagnostic emitted spans the parameter pattern, even for non-ident patterns).

I'm using cargo 1.91 and proptest 1.9.0.

Perhaps you're using a different command (other than cargo test) to generate that diagnostic output? Hard to imagine how that would change it though...