laentropia/Calculator
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Rework Lexer #10

New Issue
Closed
opened 2026-04-30 10:20:55 -06:00 by laentropia · 0 comments
laentropia commented 2026-04-30 10:20:55 -06:00
Owner
Copy Link

What?

Currently the lexer is very poorly written, while it now uses generic Arrays it stills is very bad and a rewrite this early will be good for the overall project health

Why?

Well, it is not sufficient, is not scalable for new operands, it takes responsability for ensuring structure, something that the parser should do. In generall it can be improved in many ways and that is the goal.

How?

I'm going to reserach about how to write a good lexer, specifically one that pairs well with pratt parsing (just need it to work fine i guess) so that it's more compatible and can be better tested.

# What? Currently the lexer is very poorly written, while it now uses generic Arrays it stills is very bad and a rewrite this early will be good for the overall project health # Why? Well, it is not sufficient, is not scalable for new operands, it takes responsability for ensuring structure, something that the parser should do. In generall it can be improved in many ways and that is the goal. # How? I'm going to reserach about how to write a good lexer, specifically one that pairs well with pratt parsing (just need it to work fine i guess) so that it's more compatible and can be better tested.
laentropia added this to the First working version of calculator milestone 2026-04-30 10:20:55 -06:00
laentropia added the Kind/Enhancement
Priority
Critical
1
 labels 2026-04-30 10:20:55 -06:00
laentropia self-assigned this 2026-04-30 10:20:55 -06:00
laentropia added this to the Calculator project 2026-04-30 10:20:55 -06:00
laentropia moved this to In Progress in Calculator on 2026-04-30 10:21:34 -06:00
laentropia moved this to Done in Calculator on 2026-05-12 20:09:27 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Enhancement
Priority
Critical
1
Milestone
No items
No Milestone First working version of calculator
Projects
Clear projects
No project Calculator
Assignees
Clear assignees
laentropia
No Assignees laentropia
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: laentropia/Calculator#10
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?