You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both ds's set as data.table's but in the second form, ds lacks selfref.
AFAIK setalloccol() is shallow copying ds, but then setDT fails to reassign it to the symbol ds because not recognizing 'get0' bindimg.
Arguably there is no easy way to detect the binding for every possible call that returns a data.table bound to a symbol, so I think setDT should warn when it is unable to assign it back -if a shallow copy is made-. or if ds lacks selfref before returning.
However, x does have it, and thus identical(ds, x) fails in second case.
Related perhaps #6754
The text was updated successfully, but these errors were encountered:
I think in this case we can continue the kludge pretty easily -- there's already logic for get(), it was just written before get0() existed (? or at least was more well-known):
Reading #6862 I found this behaviour:
Both
ds
's set as data.table's but in the second form,ds
lacks selfref.AFAIK
setalloccol()
is shallow copying ds, but then setDT fails to reassign it to the symbolds
because not recognizing 'get0' bindimg.Arguably there is no easy way to detect the binding for every possible call that returns a data.table bound to a symbol, so I think setDT should warn when it is unable to assign it back -if a shallow copy is made-. or if
ds
lacks selfref before returning.However,
x
does have it, and thusidentical(ds, x)
fails in second case.Related perhaps #6754
The text was updated successfully, but these errors were encountered: