-
-
Notifications
You must be signed in to change notification settings - Fork 50
Feat/better parser position tracking #571
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
Conversation
…r del nodes in ASTLowerer
…cs, to move some state out of the way
…make it shorter and clearer
… of the end position of an error (no end = whole line)
…tem that can be shared with the error context
…setFilename/line/col
…tead of a big hacky optional expr & symbol & symbol size (that can or cannot match the size of the symbol)
Static analysis reportLizard reportListing only functions with cyclomatic complexity >= 15 or NLOC >= 100 or parameters >= 6.
Report about files you didn't modify in this PR
CppCheck report
Report files about files you didn't modify in this PR
|
CodSpeed Performance ReportMerging #571 will degrade performances by 6.45%Comparing Summary
Benchmarks breakdown
|
b9817b9 to
582ae8a
Compare
Fuzzing report/usr/local/bin/afl-whatsup status check tool for afl-fuzz by Michal Zalewski Summary statsCycles without finds : 0 [+] Captured 46734 tuples (map size 218048, highest value 255, total values 425618956) in '/dev/null'. |
Description
Finally storing the end position of our nodes allowed me to remove big ugly hacks in the diagnostics generation.
Checklist
I have updated the documentation if needed (on https://github.com/ArkScript-lang/website, content/docs/)not needed, only internal changesI have added tests that prove my fix/feature is workingnot needed, all edge cases are covered by the existing tests