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
Now the code block surrounded by %{ and %} is output before the token type declaration in .fs file. This prevents error handler from using token type directly and requires boxing/unboxing trick. Outputting the code block after the token type declaration and related helper functions such as token_to_string can simplify writing rich error handlers which depend on token type. And only drawback I can see is that if the code block opens a namespace, this opened namespace will not be available in token types. But it is not a problem really, especially because the code block is not output to the .fsi file and .fsi code will not be vaild either if token elements use namespaces opened in code block.
The text was updated successfully, but these errors were encountered:
Now the code block surrounded by
%{
and%}
is output before the token type declaration in .fs file. This prevents error handler from using token type directly and requires boxing/unboxing trick. Outputting the code block after the token type declaration and related helper functions such astoken_to_string
can simplify writing rich error handlers which depend on token type. And only drawback I can see is that if the code block opens a namespace, this opened namespace will not be available in token types. But it is not a problem really, especially because the code block is not output to the .fsi file and .fsi code will not be vaild either if token elements use namespaces opened in code block.The text was updated successfully, but these errors were encountered: