weird indentation for line comments between expr and semicolon

[rszyma]

Description

This is a bit of an edge case, where indentation doesn't feel right. I suspect not many people write comments like this, but still, there's now for sure at least 1 person affected (hi!).

FWIW, inherit (that has many items) is already being formatted similarly to what I think as "expected output" for my example.

Small example input

{ pkgs }:
{
  nix.package =
    # pkgs.nixVersions.stable
    pkgs.nixVersions.git
    # inputs.nix-git.packages.${pkgs.system}.default
    ;
}

Expected output

(no changes)

{ pkgs }:
{
  nix.package =
    # pkgs.nixVersions.stable
    pkgs.nixVersions.git
    # inputs.nix-git.packages.${pkgs.system}.default
    ;
}

Actual output

{ pkgs }:
{
  nix.package =
    # pkgs.nixVersions.stable
    pkgs.nixVersions.git
  # inputs.nix-git.packages.${pkgs.system}.default
  ;
}

[MattSturgeon]

I believe this is a weird side-effect of the standard for = bindings:

For each binding value, if only the first and last line are not indented, the absorbed style is used, otherwise newline and indent.

If we ignore the comment's indentation, all lines of code within the binding are indented, allowing the final line (the ;) to use the "absorbed" style. Meaning it uses the same level of indentation as the first line.

---

This rule is intended to allow

{
  foo =
    {
      hello = "world";
    };
}

to be "absorbed" into the binding as:

{
  foo = {
    hello = "world";
  };
}

[piegamesde]

Experimental fix in #318