🐞️ Bug: Single line comments lex wrongly #173

Closed
opened 2024-04-17 11:41:40 +01:00 by deavmi · 1 comment
Owner

Purpose ✍️

There is a bug shown as such below. The lexing fails and consumes some stuff.

image

Cases

Broken

It seems if the comment token is followed directly then it fails.

// Hello
int p;

Working

If there are some characters after the \n then it seems fine:

// Hello

int p;
## Purpose ✍️ There is a bug shown as such below. The lexing fails and consumes some stuff. ![image](/attachments/9af8c976-405e-4e1d-949b-88d598615463) ## Cases ### Broken It seems if the comment token is followed directly then it fails. ```d // Hello int p; ``` ### Working If there are some characters after the `\n` then it seems fine: ```d // Hello int p; ```
154 KiB
deavmi added this to the Basics milestone 2024-04-17 11:41:40 +01:00
deavmi added the
lexer
label 2024-04-17 11:41:40 +01:00
gusmeyer was assigned by deavmi 2024-04-17 11:41:40 +01:00
deavmi added this to the Lexer project 2024-04-17 11:41:40 +01:00
deavmi changed title from Bug: Single line comments lex wrongly to 🐞️ Bug: Single line comments lex wrongly 2024-04-17 11:43:10 +01:00
deavmi added reference vardec_varass_dependency 2024-04-17 16:09:22 +01:00
deavmi removed reference vardec_varass_dependency 2024-04-17 16:09:27 +01:00
deavmi added reference bugfix/single_line_comment_bug 2024-04-18 16:39:55 +01:00
deavmi added the due date 2024-04-19 2024-04-18 16:40:11 +01:00
Author
Owner

BasicLexer

  • Bug fix for single-line comments consuming first character on next line
BasicLexer - Bug fix for single-line comments consuming first character on next line
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

2024-04-19

Dependencies

No dependencies set.

Reference: tlang/tlang#173
No description provided.