Automatically create trait dependencies (trait dependency injection) #5
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.
This PR brings automatic trait dependencies injection with cyclic dependency detection
Using this
Healthable
trait : it depends on aKillable
and aLoggable
. When assigning this trait to an object, if it is already killable or loggable, those traits are automatically injected to theHealthable
instance. Else, they are automatically instantiated (recursively!) and saved into the receiver for futur usage.This simplify trait usage, and guarantee that an object owns one and only one instance of each trait.
Cyclic dependency error/detection: