-
-
Notifications
You must be signed in to change notification settings - Fork 4
Add --debug-tokens Option to Print Token List #189
Copy link
Copy link
Open
Labels
enhancementA request for a new feature or improvement.A request for a new feature or improvement.feature requestA request for a new feature or functionality.A request for a new feature or functionality.good first issueIssues that are good for newcomers or first-time contributors.Issues that are good for newcomers or first-time contributors.
Metadata
Metadata
Assignees
Labels
enhancementA request for a new feature or improvement.A request for a new feature or improvement.feature requestA request for a new feature or functionality.A request for a new feature or functionality.good first issueIssues that are good for newcomers or first-time contributors.Issues that are good for newcomers or first-time contributors.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Backlog
Background:
This feature aims to add a debug option to the Wave CLI that prints the list of tokens generated by the lexer before parsing. It’s designed to help new contributors understand how the lexer works and get familiar with the CLI argument parsing structure. This is a perfect starting point for first-time contributors who want to explore the internals of
lexer.rs.Expected Behavior:
When running a Wave program with the
--debug-tokensflag, e.g.,the CLI should output the list of tokens generated from the input file. The normal execution flow should continue afterward. The token list should be printed in a readable format, one per line.
User Scenarios:
Additional Information:
Difficulty: Easy
Relevant files:
lexer.rs, CLI parsing moduleExample output:
This flag is purely for debugging and has no effect on actual program behavior.
Goal: Lower the entry barrier and improve understanding of Wave's internal structure.