I missed this comment. That is because if we are after the first line of a block comment that spans multiple lines, the string returned from the context actually starts from the char 0, so every whitespace before the comment is included in the string and get the correct type of comment. So if there are whitespaces at the start of the string and has a type of comment we know that it is a block comment. The only case where we don't know what happens is when the string starts with a line comment prefix.

If we have:
```
/* comment
 |  // line comment
*/
```
The string in the context at the cursor is actually `    // line comment` and the position starts on the column 0. If there wasn't a block comment surrounding the line comment, the string would be `// line comment` and the position wouldn't start on the column 0.

Now if we have:
```
/* comment
// |line comment
*/
```
You can't tell, at the cursor context, if is a line comment or a block comment.