Block comment problem
See original GitHub issueWhen doing this thing :
/**/
/**/
/**/
function A()
skip
/**/
Both of them gave me syntax error, even it seem to be no problem.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Block Comments are a Bad Idea
The other notation for comments is block comments, ... The problem occurs when we comment out code that already contains a block comment:...
Read more >Block comments in user script not working properly [19377]
The Block comments in the user script are not working properly. Detail Block comments should treat all of the lines between the start...
Read more >Block comments - Bartleby
Explanation- The block comments can have any number of lines of strings as comments, it can even have a single line of comment...
Read more >Remove Comments - LeetCode
The string "/*" denotes a block comment, which represents that all characters until the next (non-overlapping) occurrence of "*/" should be ignored. (Here, ......
Read more >How to Comment Out Multiple Lines in Python - freeCodeCamp
The real workaround for making multi-line comments in Python is by using docstrings. If you use a docstring to comment out multiple line...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the main problem here was, that Vscode did not highlight the comments correctly. I pushed an update to fix this now.
Here is how your example looks like now:
The comment starts with
/**
and ends with the next*/
after that.Also important to know: Hotdoc comments are not like other comments – they can only appear at certain places in the source code (e.g. in front of a function) and when used in different places you get a syntax error.
Ah I see, pretty neat feature, thanks for your explanation.