Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parser: update file path fields; use more expressive name for file path, remove obsolete file_name_dir field #21202

Merged
merged 2 commits into from
Apr 7, 2024

Conversation

ttytm
Copy link
Member

@ttytm ttytm commented Apr 6, 2024

Updates file field names on the parser. Main concern was file_name holding the path and same data field is e.g. used on the scanner named file_path. Imho simpler to understand during development when reading file_path and understanding assignments to path related fields then doing so with file_name.

@ttytm ttytm changed the title parser: use more expressive names for file path fields parser: use more expressive name for file path field, remove obsolete field Apr 7, 2024
@ttytm ttytm changed the title parser: use more expressive name for file path field, remove obsolete field parser: update file path fields; use more expressive name for file path, remove obsolete dir path field Apr 7, 2024
Copy link
Member

@spytheman spytheman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent work.

@spytheman spytheman changed the title parser: update file path fields; use more expressive name for file path, remove obsolete dir path field parser: update file path fields; use more expressive name for file path, remove obsolete file_name_dir field Apr 7, 2024
@spytheman spytheman merged commit f7d178d into vlang:master Apr 7, 2024
56 checks passed
@ttytm ttytm deleted the parser/vars branch April 7, 2024 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants