Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@Emphiliis it's a way hackers communicate. you're not 1337 enough to understand
-
@irene well, I only use them when debugging stuff. Otherwise I don't keep commented code at all.
-
@devTea if I recall it correctly the compiler gave the same error. Each Nested block comment definitely needs to be closed..
-
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
Related Rants
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..
rant
kotlin
nested block comments