kscript comment-style directives are marked as errors with ktlint

[0legg]

Similar to #212 — kscript uses comment-style directives and relying on no space after the double slash.

I'm not sure whether this issue belongs to ktlint of kscript though — my gut feeling is it's kscript who needs to adopt the change, but I'll cross-create tickets in both repos.

Ref kscripting/kscript#153

[0legg]

https://github.com/google/google-java-format/blob/4fa9d4967170109b1f8b238c12bb42ee9d26ba88/core/src/main/java/com/google/googlejavaformat/java/JavaCommentsHelper.java#L105-L108 For reference, GCF excludes few predefined annotation-alike comments from formatting, ktlint does the same for noinspection.

[shyiko]

To summarize:

right now user has an option to

• turn off comment-spacing check by prepending /* ktlint-disable comment-spacing */ at the top of the script.
• (or) use @file:* instead of //... (kscript comment-style directives are marked as errors with ktlint kscripting/kscript#153 (comment)).

ktlint could

• provide a way to exclude certain patterns (e.g. //(DEPS|ENTRY|...)) (this would require a config file which we don't currently have)
• auto-detect kscript (#!/usr/bin/env kscript) (allow //(DEPS|ENTRY|...) when detected) (https://github.com/holgerbrandl/kscript#use-entry-to-run-applications-with-main-method would not be covered)

kscript could

• support //\s*(DEPS|ENTRY|...) (kscript comment-style directives are marked as errors with ktlint kscripting/kscript#153 (comment)).
• support // kscript-deps ..., // kscript-entry ..., etc.