-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add discussion of incomplete types and constraints for Hagenberg meeting #513
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #513 +/- ##
==========================================
+ Coverage 99.55% 99.59% +0.04%
==========================================
Files 7 11 +4
Lines 669 743 +74
Branches 75 75
==========================================
+ Hits 666 740 +74
Misses 3 3 ☔ View full report in Codecov by Sentry. |
…alue_types into dev-jbcoe-hagenberg-presentation
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.
Review comments and amend.
…alue_types into dev-jbcoe-hagenberg-presentation
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.
Looks good.
|
||
```c++ | ||
struct Number {}; // Complete type. | ||
Whilst appealing, this approach works badly in composition with other types. |
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 find 'works badly' uncompelling without the context, perhaps 'encounters problems'.
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.
How about:
Whilst appealing, this approach is problematic when used in composition with other types.
No description provided.