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
BlobTree currently iterates values for much the same reasoning that Dictionaries.jl does (broadcast support, etc). For cases where the name is important this might seem inconvenient. But individual Blob or BlobTree elements in the iteration also know their names via basename which makes it possible to extract names where necessary. To resolve this it's probably best to translate some examples of data processing code to the BlobTree API and see whether pairs() or values() is desired for iteration.
As a side note, having values know their own keys via basename is quite an oddity for a dictionary-like datastructure. Is this a problem in itself? Generally, Blob is only a lazy reference to data held outside Julia. An individual Blob object presumably won't be an element of two different BlobTrees — it needs to cause a copy in the background. Perhaps this isn't so bad, then.
The text was updated successfully, but these errors were encountered:
BlobTree
currently iterates values for much the same reasoning that Dictionaries.jl does (broadcast support, etc). For cases where the name is important this might seem inconvenient. But individualBlob
orBlobTree
elements in the iteration also know their names viabasename
which makes it possible to extract names where necessary. To resolve this it's probably best to translate some examples of data processing code to theBlobTree
API and see whetherpairs()
orvalues()
is desired for iteration.As a side note, having values know their own keys via
basename
is quite an oddity for a dictionary-like datastructure. Is this a problem in itself? Generally,Blob
is only a lazy reference to data held outside Julia. An individualBlob
object presumably won't be an element of two differentBlobTree
s — it needs to cause a copy in the background. Perhaps this isn't so bad, then.The text was updated successfully, but these errors were encountered: