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
If you traverse a file containing CIDs, you might want to keep track of your current position. Currently read_bytes() only returns the new CID. As varints are involved, you cannot tell by how many bytes the reader was advanced. Hence I propose extending read_bytes() to also return the number of byte read.
The text was updated successfully, but these errors were encountered:
I was building an index on top of a file that stores CID + data tuples. I wanted to get the byte offset of the data without asking the reader about its current position after it read a CID.
If you traverse a file containing CIDs, you might want to keep track of your current position. Currently
read_bytes()
only returns the new CID. As varints are involved, you cannot tell by how many bytes the reader was advanced. Hence I propose extendingread_bytes()
to also return the number of byte read.The text was updated successfully, but these errors were encountered: