Skip to content

Conversation

@c42f
Copy link
Member

@c42f c42f commented Apr 26, 2023

The tokenizer can't really solve this case, it needs help from the parser. ie, tighter coupling of tokenizer and parser.

However the workarounds here avoid crashing the parser and even gives the right result in most cases.

Close #186. Close #25

The tokenizer can't really solve this case, it needs help from the
parser. ie, tighter coupling of tokenizer and parser.

However the workarounds here avoid crashing the parser and even gives
the right result in most cases.
@codecov
Copy link

codecov bot commented Apr 26, 2023

Codecov Report

Merging #251 (54de76f) into main (1515d8f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #251   +/-   ##
=======================================
  Coverage   96.47%   96.48%           
=======================================
  Files          15       15           
  Lines        3919     3925    +6     
=======================================
+ Hits         3781     3787    +6     
  Misses        138      138           
Impacted Files Coverage Δ
src/parser.jl 98.25% <100.00%> (+<0.01%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@c42f
Copy link
Member Author

c42f commented Apr 26, 2023

Eh let's go with this. It's not pretty, but it'll do for now.

@c42f c42f merged commit ec705ed into main Apr 26, 2023
@c42f c42f deleted the c42f/workaround-ambiguous-primes branch April 26, 2023 06:48
c42f added a commit to JuliaLang/julia that referenced this pull request Oct 17, 2025
…g/JuliaSyntax.jl#251)

The tokenizer can't really solve this case, it needs help from the
parser. ie, tighter coupling of tokenizer and parser.

However the workarounds here avoid crashing the parser and even gives
the right result in most cases.
topolarity pushed a commit to JuliaLang/julia that referenced this pull request Nov 14, 2025
…g/JuliaSyntax.jl#251)

The tokenizer can't really solve this case, it needs help from the
parser. ie, tighter coupling of tokenizer and parser.

However the workarounds here avoid crashing the parser and even gives
the right result in most cases.
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.

Errors from fuzz testing Prime parsing issues

1 participant