Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Test Explorer in VS Code Extension and
@Test()
Attribute #2059Test Explorer in VS Code Extension and
@Test()
Attribute #2059Changes from 29 commits
b79c31e
1c09783
54eb209
e6a0941
0495a6d
eae1b4d
759036f
cec4bf9
ad7d3e2
d9f288d
9ec9f41
a03ed14
c11476a
b247c35
e75f65b
131a341
b52ad25
180368e
e960916
7d2aadc
ac8bfd7
c22d14d
5a28ef1
16a2aed
214097c
adbc4b2
5b6a1f8
7cee532
be64105
e34b7d2
fa1ca42
790c29b
9d0190c
38e0f4b
43f4e17
bcd6d34
5421cb2
804fb0b
ffab724
cca48b5
eea9581
540de0b
f171141
8255955
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So does this just silently drop a callable with the Test attribute if it happens to be generic? No warning or error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error is detected in
qsc_passes
. Returning an error here doesn't show a pretty error to the user, so instead we detect it in passes and produce a spanned error. This pattern was suggested by @swernli and I think it is cleaner than returning an error here, which just prints an unspanned error in a VS Code dialog box.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I saw those checks there. Just wondering the value of even testing for it here also, as the project is already in error from the other pass that detects these, and thus I assume shouldn't run anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It just prevents the test from showing up in the list. The pass doesn't filter out the callables from the HIR, because we prefer to preserve as much of the AST as possible for error recovery in passes. So even in an error state, the compilation does return some HIR for a good user experience. We can't let those invalid callables show up in the test explorer right?