-
Notifications
You must be signed in to change notification settings - Fork 9
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
Could path,DelayedArray-method
just defer to the path()
of its @seed
?
#120
Comments
Hmm.. even with the dedicated
Adding the dedicated
Need to implement Working on that change now... sessionInfo()
|
Revisit implementation of the path() getter (and setter) for DelayedOp. The new implementation is recursive so will acknowledge path() methods defined for custom DelayedOp derivatives like the path() getter defined for ReloadedArraySeed objects in the alabaster.matrix package. Should address #120
Done in DelayedArray 0.33.3 (see commit a782607). With this version:
You should no longer need the |
Thanks, looks good on my end. |
Curently
path(<DelayedArray>)
just callspath(<DelayedOp>)
, which effectively tries to callpath(seed(object))
. Could a dedicatedpath,DelayedArray-method
be added that callspath(object@seed)
?As per the conclusion of #119, my
ReloadedArraySeed
class now inherits fromDelayedUnaryIsoOp
, but itspath()
method is not respected when callingpath(<ReloadedArray>)
. This is because theseed()
call follows the new inheritance path for theDelayedUnaryIsoOp
, retrieving theReloadedArraySeed
's seed instead of theReloadedArraySeed
itself. Subsequently, thepath()
call uses the seed's method instead of my customReloadedArraySeed
method, which is not intended.The proposed change to
path(object@seed)
should not affect any existing behavior. If@seed
is aDelayedOp
,path()
will still callseed()
to get the underlying seed; and if@seed
is something else, directly using itspath()
method is arguably less surprising than whatever we might get from followingseed()
(if it even runs at all, e.g., error from multiple seeds).The text was updated successfully, but these errors were encountered: