Feature request: Please allow consecutive spaces prior to a trailing comment.

[nallick]

Version: 0.40.4

Consecutive spaces within code are frequently different than consecutive spaces before an inline comment. For example, here the comment may be intended to have some extra space to separate it from the code, but it's still desirable to remove the extra space in the code.

var    i =   1      // one based index

Here's typical example were the space before the comment may be desirable.

enum Algorithm: Int {
    case aes = 0        // kCCAlgorithmAES
    case des            // kCCAlgorithmDES
    case tripleDES      // kCCAlgorithm3DES
    case cast           // kCCAlgorithmCAST
    case rc4            // kCCAlgorithmRC4
    case rc2            // kCCAlgorithmRC2
    case blowfish       // kCCAlgorithmBlowfish
}

versus:

enum Algorithm: Int {
    case aes = 0 // kCCAlgorithmAES
    case des // kCCAlgorithmDES
    case tripleDES // kCCAlgorithm3DES
    case cast // kCCAlgorithmCAST
    case rc4 // kCCAlgorithmRC4
    case rc2 // kCCAlgorithmRC2
    case blowfish // kCCAlgorithmBlowfish
}

[nicklockwood]

@nallick I see your point, however I don't think this is unique to inline comments, e.g. this pattern is quite common too:

struct Foo {
  var someVar              = 4
  var aLongerVariable      = 6
  var foo                  = 7
}

I'm not yet sure what the best way to handle this is, but I probably need a solution for both.

[nallick]

That's fair