Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried to figure out that weird sphinx error (because I hit it in pytential as well):
From what I can tell, the issue was in
where
Expression
contained anExpressionNode
. Sphinx got confused because it was looking forExpressionNode
in the current module set topymbolic.typing
and failing. No idea why it would look there.. maybe because the annotation is a string and it didn't have any choice? The exact same thing works forArithmeticExpression
becauseExpressionNode
is in the same module (I think?).Anyways, adding a fake reference fixes that sort of issue
Besides that, I moved some docs around because for some reason Sphinx wasn't showing them..