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

Work around "the lexer hack" #115

Open
ForNeVeR opened this issue Mar 27, 2022 · 0 comments
Open

Work around "the lexer hack" #115

ForNeVeR opened this issue Mar 27, 2022 · 0 comments
Labels
area:compiler Related to code compilation or type checking area:parser The C language parser Cesium uses kind:refactor Internal changes not affecting the compiler behavior status:help-wanted Open for contributors

Comments

@ForNeVeR
Copy link
Owner

ForNeVeR commented Mar 27, 2022

Currently, certain syntax constructs have to be parsed as AmbiguousBlockItem, and then resolved in emit time.

I don't like the current solution (since it introduces a lot of noise into the code), and would like to see a more clean solution. At least, let's get rid of these ugly direct type casts somehow.

See // TODO[#115] in the code to find the related issues.

See also: a dicsussion LanguageDev/Yoakke#139 which lead to the current solution.

@ForNeVeR ForNeVeR added status:help-wanted Open for contributors area:compiler Related to code compilation or type checking kind:refactor Internal changes not affecting the compiler behavior area:parser The C language parser Cesium uses labels Mar 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:compiler Related to code compilation or type checking area:parser The C language parser Cesium uses kind:refactor Internal changes not affecting the compiler behavior status:help-wanted Open for contributors
Projects
None yet
Development

No branches or pull requests

1 participant