Streaming lexer #106

Open
opened 2023-03-08 14:28:49 +00:00 by deavmi · 3 comments
Owner

What is this?

This issue pertains to the feature addition that requires @rany implement a new lexer that works on the source code that is read in (one shot, we could discuss updating the interface provided by LexerInterface in #105 to read the source bit-by-bit) and lexers the next token only when nextToken() is called.

You will need to cache stuff as previousToken() is a thing.

# What is this? This issue pertains to the feature addition that requires @rany implement a new lexer that works on the source code that is read in (one shot, we could discuss updating the interface provided by `LexerInterface` in #105 to read the source bit-by-bit) and lexers the next token only when `nextToken()` is called. You will need to cache stuff as `previousToken()` is a thing.
Ghost was assigned by deavmi 2023-03-08 14:28:56 +00:00
deavmi added a new dependency 2023-03-08 14:29:17 +00:00
deavmi added a new dependency 2023-03-08 14:29:21 +00:00
Author
Owner

🔐️ Locking for now till I stabilize stuff and onboard @rany

🔐️ Locking for now till I stabilize stuff and onboard @rany
deavmi locked and limited conversation to collaborators 2023-03-08 14:30:44 +00:00
deavmi added this to the Clean ups milestone 2023-03-08 14:32:21 +00:00
deavmi added the
qol
lexer
labels 2023-03-08 14:32:26 +00:00
deavmi added this to the Lexer project 2023-03-08 14:32:36 +00:00
deavmi removed this from the Lexer project 2023-03-08 14:32:42 +00:00
deavmi added this to the Parser project 2023-03-08 14:32:48 +00:00
deavmi added reference feature/lexer_interface 2023-04-20 11:05:27 +01:00
deavmi removed a dependency 2023-04-20 13:53:25 +01:00
Author
Owner

I should just do this, in near future.

I should just do this, in near future.
deavmi removed reference feature/lexer_interface 2023-07-09 11:42:05 +01:00
Ghost was unassigned by deavmi 2023-07-09 11:42:11 +01:00
Author
Owner

This will be worked on later, not all too urgent for now at the very least.

This will be worked on later, not all too urgent for now at the very least.
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'.

No due date set.

Depends on
Reference: tlang/tlang#106
No description provided.