Fix start&top implementation in typechecker#2551
Conversation
This reverts commit 570bd8e.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2551 +/- ##
=======================================
Coverage 46% 46%
- Complexity 6725 6731 +6
=======================================
Files 794 794
Lines 65923 65923
Branches 9888 9888
=======================================
+ Hits 30837 30842 +5
+ Misses 32696 32691 -5
Partials 2390 2390 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
jurgenvinju
left a comment
There was a problem hiding this comment.
Looks good. Needs an integration test.
|
|
@jurgenvinju this is your own code ;) I merely did some git cooking to extract it from a different PR. |
|
@PaulKlint should we use typepal's "predefine" functionality instead of constructing an artificial field location for "top"? Same for the entire start rule. Should we use predefine for that as well? |



This PR continues the work in #2499 (that was merged to main a bit too soon) to fix #2496
start[X]andX(inasubtype,alub,aglb).topcontextFreeSyntaxrole is expected by adding arolefield to thestartATypesyntaxrule forXthat has astartmodifier:start[X] = X;start[X] = X top;start[X] = L X L;isStart*andgetStart*that were used for detecting the old special casesTogether these changes solve a small number of known issues with start symbols, and a larger number of previously undetected issues.