Wrong range when request at edited std

rust-analyzer version: 2026-07-20 tag release (2026-07-13 no this bug)

rustc version: rustc 1.97.0-nightly (36ba2c771 2026-04-23)

editor or extension: Vim coc-rust-analyzer or naked rust-analyzer

code snippet to reproduce:
In ~/.rustup/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/non_null.rs

#[stable(feature = "nonnull", since = "1.25.0")]
#[repr(transparent)]
#[rustc_nonnull_optimization_guaranteed]
#[rustc_diagnostic_item = "NonNull"]
pub struct NonNull<T: PointeeSized> {
    pointer: crate::pattern_type!(*const T is !null),
    i$0
}

Outputs:

Error on resolve complete item from rust-analyzer: {
  "label": "impl",
  "kind": 14,
  "preselect": true,
  "sortText": "7ffffff6",
  "filterText": "impl",
  "insertTextFormat": 2,
  "textEdit": {
    "newText": "impl $1 {\n    $0\n}",
    "insert": {
      "start": { "line": 76, "character": 0 },
      "end":   { "line": 75, "character": 5 }
    },
    "replace": {
      "start": { "line": 76, "character": 0 },
      "end":   { "line": 76, "character": 0 }
    }
  }
}
ResponseError: Received a completion with overlapping edits, this is not LSP-compliant

Better reproduction

1. Insert a space before pub struct NonNull
2. Cursor on NonNull, use hover doc, response range is based on the original, not the edited document

Expect "NonNull", Actual " NonNul"

Start by reproducing the Better reproduction with the completion and hover requests, then trace rust-analyzer's LSP text-edit and range handling. Compare the response ranges with the edited document after inserting a space before pub struct NonNull. Done means completion and hover ranges use the edited document and no overlapping edits or shifted text are returned.