It might be useful to have an ability to exclude some classes from lazy properties instantiation #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.
It was decided to derive
<BMLazy>
protocol in subclasses and not to require its mentioning in them. Anyhow, sometimes it might be useful to 'skip' lazy properties instantiation for some classes in this hierarchy. So, from now on it's possible to use<BMLazyExclude>
protocol to do that. All the properties declared in those 'excluded' classes would not be taken into account when we collect@dynamic
properties for lazy instantiation.Example usage
In this hierarchy class
A
is defined as lazy so its propertya
would be lazily instantiated. ClassB
would also be lazy (as it derives<BMLazy>
protocol fromA
) so its propertyb
would be lazily instantiated as well as inherited propertya
.C
is defined as<BMLazyExclude>
and inheritsB
so its propertyc
would not be lazily instantiated whilea
andb
would still be lazily instantiated.