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
I've got some use cases for macros where I end up producing an expansion that calls other macros, and those other macros may produce diagnostics. Right now, they end up pointing to the temporary file containing the first macro's expansion rather than to the original source. This makes sense in the general case, however in my case I know exactly where in the original macro expression/declaration the problem lies.
I can specify an AbsolutePosition when creating a Diagnostic, but I can't specify a filename or file ID. If I could, then I could ensure my diagnostics present correctly at compile time.
The text was updated successfully, but these errors were encountered:
I've got some use cases for macros where I end up producing an expansion that calls other macros, and those other macros may produce diagnostics. Right now, they end up pointing to the temporary file containing the first macro's expansion rather than to the original source. This makes sense in the general case, however in my case I know exactly where in the original macro expression/declaration the problem lies.
I can specify an
AbsolutePosition
when creating aDiagnostic
, but I can't specify a filename or file ID. If I could, then I could ensure my diagnostics present correctly at compile time.The text was updated successfully, but these errors were encountered: