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
Current v07-draft branch uses limit() setLimit(...) methods to obtain the written data range. Instead, we should provide MessageBuffer slice(int offset, int len) method to make MessageBuffer immutable (except its memory contents).
I simply removed limit parameter from MessageBuffer, and provide slice() method. Memory management of generated slices need to be discussed in another ticket.
Activity
Fixes #90: Using MessageBuffer.slice() instead of using setLimit
xerial commentedon May 15, 2014
I simply removed limit parameter from MessageBuffer, and provide slice() method. Memory management of generated slices need to be discussed in another ticket.
frsyuki commentedon May 15, 2014
👍