Fix single_range_in_vec_init FP for explicit Range

[profetia]

Closes #16042
Closes #16044

changelog: [single_range_in_vec_init] fix FP for explicit Range

[rustbot]

r? @samueltardieu

rustbot has assigned @samueltardieu.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[profetia]

Also closes #16044

[ada4a]

imo it would be better to preserve what the user wrote, i.e. if the original expression was a range, then we should use that in the suggestion as well

[Jarcho]

We shouldn't be linting the explicit constructor. The lint is meant to catch vec![1..4] being used when vec![1, 2, 3] was intended.

[profetia]

You are right. It should be considered as a FP instead

[samueltardieu]

Also, it looks like the @no-rustfix can be removed.

[profetia]

@samueltardieu Updated. Thank you!

[rustbot]

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.