Conversation
|
@deoxxa ping 🔔 |
|
@SamyPesse Is there really a need for |
|
@arthurschreiber Yes, we probably can, I'll run some tests and get back to you in a few minutes. |
|
@arthurschreiber
During unit tests both are equal since we create a new instance for each I can try to write a cleaner solution, for example something where |
|
@SamyPesse Hi! I have contributed one solution that doesn't use offset #24. Personally, I think in many cases knowing the offset would force the user into "doing the math" by hand, which is usually not comfortable and messy. But, for the sake of universality, yes, knowing the offset should be there for last resort. |
This PR adds a “offset” property (readable, not writable), to indicate the current offset in the buffer/stream.
I need this PR when using Dissolve to parse a git packfile, where I need to record a map {offset: Object} for future references.