Why the heck would you allow (or need) nested block comments? Imo this is a major design flaw in the kotlin linter.

I always use /*... //*/ so I can remove the comment starter w/o having to remove the comment end, but kotlin just starts a second, nested comment there.

Java, C, Cpp, C#, JS,... Not one of these uses nested block comments. I think jetbrains was just lazy?

I mean, I know why such stuff happens. I also developed DSLs in MPS, but there sure are ways to go around such things..

  • 3
    No, really, please tell my why I'd need nested block comments.
  • 4
    @Emphiliis it's a way hackers communicate. you're not 1337 enough to understand
  • 2
    @irene well, I only use them when debugging stuff. Otherwise I don't keep commented code at all.
  • 3
    Isn’t this the IDE/Text editor fault?
  • 2
    @devTea if I recall it correctly the compiler gave the same error. Each Nested block comment definitely needs to be closed..
  • 2
    @Emphiliis well, fuck kotlin then
  • 2
    Nested block comments are awesome because you can comment out a larger section that contains already commented out code. Just put a space between the line and the closing block comment because that's just how a lexer works
Add Comment