-
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
Trait inheritance #11
Comments
Do the easier first, with examples of proper use -- your package is of much wider applicability if stuff that is in the land of @generated is done behind the scene. |
Some initial work on this branch: https://github.com/mauro3/SimpleTraits.jl/tree/m3/subtraits |
Thanks for the subtrait effort. Why did Not need to become concrete? fyi, re line 114, to distinguish CleanCode from cleanCode ... title case On Wed, Oct 19, 2016 at 11:07 AM, Mauro [email protected] wrote:
|
I added a test that all trait parameters need to be specified for it to be a valid trait: SimpleTraits.jl/src/SimpleTraits.jl Line 94 in 2d5112b
But that test only works if Not is not abstract. I'm not sure what the original reason was to make it abstract. The test pass, so I just changed it.
I'm kinda aware of camelCase but no true camel case is used in Julia so I feel its clear enough. |
I'll try it out. On Wed, Oct 19, 2016 at 3:20 PM, Mauro [email protected] wrote:
|
Trait inheritance can be implemented with generated functions as described in https://github.com/mauro3/SimpleTraits.jl#advanced-features . This could be added to the
@traitdef
macro. One thing to ponder would be the effect of@traitimpl
: should it do checking that subtraits are defined (trickier) or should it just force it (this would be as is).The text was updated successfully, but these errors were encountered: