You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the active buildup and development of the Kipper Parser, only /* */ multi-line comments were implemented at first, only allowing the use of comments that had an explicit start and end.
This is not consistent with other languages though, where both // and /* */ are usually supported. As such, this issue proposes the implementation of single-line comments in the following format:
// ... [\n]
The end of the comment will like in other languages, such as TypeScript, Java or C#, be defined as the invisible line-end char (\n, \r\n or \r).
Exact behaviour / changes you want
Implement syntax support for single-line comments.
Resolve any bugs associated with newline recognition in the Kipper Parser.
The text was updated successfully, but these errors were encountered:
Is there an existing proposal for this?
This feature does not exist in the latest version
Proposal
Due to the active buildup and development of the Kipper Parser, only
/* */
multi-line comments were implemented at first, only allowing the use of comments that had an explicit start and end.This is not consistent with other languages though, where both
//
and/* */
are usually supported. As such, this issue proposes the implementation of single-line comments in the following format:// ... [\n]
The end of the comment will like in other languages, such as TypeScript, Java or C#, be defined as the invisible line-end char (
\n
,\r\n
or\r
).Exact behaviour / changes you want
The text was updated successfully, but these errors were encountered: