suggest code action fixes produced from diagnostics under cursor, even if they have effects elsewhere

[bend-n]

the point of this, at least for me, is mostly the
"feature(x) is unstable" errors.
this allows you to code-action fix them from the point of feature usage.

[ChayimFriedman2]

I cannot get rustc to emit fixes for unstable features used; did you verify this patch works?

[bend-n]

yeah

[ChayimFriedman2]

What was the code?

[bend-n]

const fn x() -> &'static [u8] {
    unsafe { core::intrinsics::transmute_unchecked::<u32, u8>(4) };
    todo!()
}

[Veykril]

You only get those on nightly toolchains I think

[ChayimFriedman2]

Alright. I accept the idea, but please put the new range inside Fix::ranges instead (and increase it's SmallVec size to 2).

View changes since this review

[bend-n]

should i just like. fix.ranges[1] = diagnostic.range?

[ChayimFriedman2]

No, of course not. You need to push() it.

[bend-n]

yeah but like. would there never be two things in the fix.ranges? was it basically just an option before?

[ChayimFriedman2]

No, that's why it's a vector.

[ChayimFriedman2]

Thanks!

View changes since this review