-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Adding specific error messages for invalid property on non pointer types #11748
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
Closed
yug-intel
wants to merge
17
commits into
intel:sycl
from
yug-intel:specific-error-message-for-invalid-property
Closed
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
5445994
adding static assertions for properties on non pointer type and remov…
yug-intel 508efe7
added static assertion for alignment
yug-intel d5606eb
adding negative test for checking invalid props on non pointer types
yug-intel b9be0e4
fix lint
yug-intel d5f2340
fix bug in annotated_arg_properties.cpp
yug-intel 2894df0
Using macro to save lines of code
yug-intel d323c2c
fix lint
yug-intel 2fec364
added back is_valid_property and check_property_list check
yug-intel 91aa229
added include
yug-intel 6c21846
fix lint
yug-intel fe098fe
restored all definitions for is_valid_property
yug-intel 06be97a
added include again
yug-intel f60ca37
Merge branch 'sycl' into specific-error-message-for-invalid-property
yug-intel d32a982
testing removing include
yug-intel 7e216c5
updated annotated_arg_negative.cpp test
yug-intel 6917f19
added no error limit for annotated_arg_negative.cpp
yug-intel d3a0381
testing includes
yug-intel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
I think this might not be the way we want to do this check, mainly for two reasons:
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.
I checked with Yug and it seems we didn't find a way to get the template to work with static_assert.
The problem is that the pre-processor runs before template processing so you can not get a string customized with template's type and display it on a static_assert.
Let's just create a simple Macro here and makes it a bit cleaner and it should be good to go
Uh oh!
There was an error while loading. Please reload this page.
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.
I saw the error that comes with the macro style. I disagree, we should keep Yug's original version. It is strictly better from a user's perspective.
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.
I have pushed the macro change. I talked with Abhishek offline and he is okay with it now because the error message does not contain "_key" and is now very similar to what was being printed before.