-
Notifications
You must be signed in to change notification settings - Fork 47
Conditionally include resize methods / constructors depending on type traits #191
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
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b9d38f9
Conditionally include resize methods depending on type traits
Shizcow a18f6fe
Cleaned up diff
Shizcow 10bcc67
Exposed additional constructors
Shizcow 577c059
Cleaned up indentation
Shizcow f46ed30
Mirror NeverEmpty so that compilation suceeds on GH runners
Shizcow 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
Oops, something went wrong.
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.
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.
Why, specifically, is this required? There is a general lack of documentation on what exactly a mirrored type is. This compiles fine on my local machine without disabling mirroring for this type, but fails in the runners. Why? Is disabling mirroring correct here, or is the complaint indicative of an edge case I've not considered?
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.
This is because this simple test class is detected as a "plain old data" type, and by default these are expected t be mapped to a Julia struct with the same layout, by using
map_typeinstead ofadd_type. To override this,IsMirroredTypecan be specialized. Could be better documented, indeed :)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.
Ah, that makes perfect sense. Thanks for the explanation!