-
Notifications
You must be signed in to change notification settings - Fork 37
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
Catalog and catch the main proc macro usage error before it blows up in the compilation of the macro #154
Comments
As what I understood from this is that this issue is about improving error handling The current error when wrong file name is provided to
to this improved version Code
This aligns with my understanding of the issue, but I wanted to confirm if this interpretation matches your intent. If not, could you provide some guidance or clarification to help me understand what you’re aiming for? |
@AS1100K yes this is a good start, we could merge this one as part 1 ie. invalid path or invalid RON syntax. We can start to fix the obvious stuff first and then iterate. another huge improvement we could do: Do you think also we can report a line in the RON files where the error is? |
Today if the user makes a mistake in the config for example, it doesn't compile the macro so the error is always on the macro invocation and totally dependent on what the macro is trying to compile from the broken input.
The text was updated successfully, but these errors were encountered: