The location for implicitDrops is kind of hard to read.

[wyatt-herkamp]

rust-analyzer version: rust-analyzer version: 0.4.1755-standalone (e402c49 2023-12-01)

rustc version: (eg. output of rustc -V) rustc 1.75.0-beta.5 (1a06ac5b5 2023-12-01)

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTC, RUSTUP_HOME or CARGO_HOME)

  "rust-analyzer.procMacro.ignored": {
    "tokio-macros": [
      "main"
    ],
    "async-trait": [
      "async_trait"
    ],
    "tracing-attributes": [
      "instrument"
    ],
  },
  "rust-analyzer.inlayHints.lifetimeElisionHints.enable": "skip_trivial",
  "rust-analyzer.inlayHints.lifetimeElisionHints.useParameterNames": true,
  "rust-analyzer.inlayHints.closingBraceHints.enable": false,
  "rust-analyzer.inlayHints.expressionAdjustmentHints.enable": "reborrow",
  "rust-analyzer.inlayHints.implicitDrops.enable": true, // This is the most relevant setting
  "rust-analyzer.inlayHints.expressionAdjustmentHints.hideOutsideUnsafe": true,
  "rust-analyzer.inlayHints.reborrowHints.enable": "mutable",
  "rust-analyzer.rustfmt.extraArgs": [
    "+nightly"
  ],

I think the location of drop(_) should be after the }/ curly bracket.
It makes it kind of hard to read with it shifting the curly to the right.

[Young-Flash]

interesting, I'd like to take a stab on this.

@rustbot claim