Skip to content
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

[enhancement] DSLX error messages should have more structured data about related source ranges #1382

Open
cdleary opened this issue Apr 17, 2024 · 0 comments
Labels
cleanup Tech debt reduction, factoring, consolidation, rework, etc. dslx DSLX (domain specific language) implementation / front-end enhancement New feature or request long-term-enhancement Issues that are sensible enhancements but XLS devs expect may not be addressed in the near-term

Comments

@cdleary
Copy link
Collaborator

cdleary commented Apr 17, 2024

What's hard to do? (limit 100 words)

Right now we just have one span of text that's reported for a given DSLX error message, but you can make much prettier error messages if you can have multiple distinct chunks of text with their own messages/labels.

Current best alternative workaround (limit 100 words)

Right now we just report error messages with respect to one text span and that's fine but could be better.

Your view of the "best case XLS enhancement" (limit 100 words)

We would rely on some facility like Status payloads to help get more metadata about source core ranges related to error messages out to the error printing facilities.

@cdleary cdleary added enhancement New feature or request dslx DSLX (domain specific language) implementation / front-end cleanup Tech debt reduction, factoring, consolidation, rework, etc. long-term-enhancement Issues that are sensible enhancements but XLS devs expect may not be addressed in the near-term labels Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Tech debt reduction, factoring, consolidation, rework, etc. dslx DSLX (domain specific language) implementation / front-end enhancement New feature or request long-term-enhancement Issues that are sensible enhancements but XLS devs expect may not be addressed in the near-term
Projects
None yet
Development

No branches or pull requests

1 participant