-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Use top_level_semantic
in doc spec instead of semantic
#9352
Use top_level_semantic
in doc spec instead of semantic
#9352
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good to me - though I don't have write access so I cannot merge this PR. Does this generate the exact same docs as just 'semantic'? And how kuch faster is this?
The docs generator only needs and uses top level semantic, so the result should be entirely correct. |
I'm not sure about the |
@@ -77,7 +77,23 @@ def semantic(node : ASTNode, *, warnings = nil, wants_doc = false, flags = nil) | |||
SemanticResult.new(program, node) | |||
end | |||
|
|||
def assert_normalize(from, to, flags = nil, *, file = __FILE__, line = __LINE__) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be removed, it's why CI is failing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Specs are green now 🚀
top_level_semantic
in doc spec instead of semantic
This PR adds
top_level_semantic
utility methods for compiler spec, and uses this in doc spec.crystal docs
command usestop_level_semantic
, so the spec follows it.