You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
where const CeedScalar (*q) = in; is treated as a declaration, while CeedScalar (*w) = in; and CeedScalar (*v); are treated as expression_statements.
Although the markdown syntax highlighter also treats the second CeedScalar as a function call, it really shouldn't be. The first bug (CeedScalar (*w) = in;) can be easily differentiated since a function call cannot be on the LHS of an expression statement. The second CeedScalar (*v); is probably a bit trickier.
The text was updated successfully, but these errors were encountered:
It is possible (and necessary) to declare a custom defined variable by enclosing the result in parenthesis. For example:
This results in the following syntax highlighting (in neovim):
Interestingly, the markdown parser also turns up the same result (copied below in case GH updates it):
And playground for the above example returns:
where
const CeedScalar (*q) = in;
is treated as adeclaration
, whileCeedScalar (*w) = in;
andCeedScalar (*v);
are treated asexpression_statement
s.Although the markdown syntax highlighter also treats the second
CeedScalar
as a function call, it really shouldn't be. The first bug (CeedScalar (*w) = in;
) can be easily differentiated since a function call cannot be on the LHS of an expression statement. The secondCeedScalar (*v);
is probably a bit trickier.The text was updated successfully, but these errors were encountered: