Paul Sokolovsky 5d2499c638 Add "buffer management" and "shrink" API calls to vstr.
vstr is initially intended to deal with arbitrary-length strings. By
providing a bit lower-level API calls, it will be also useful to deal
with arbitrary-length I/O buffers (the difference from strings is that
buffers are filled from "outside", via I/O).

Another issue, especially aggravated by I/O buffer use, is alloc size
vs actual size length. If allocated 1Mb for buffer, but actually
read 1 byte, we don't want to keep rest of 1Mb be locked by this I/O
result, but rather return it to heap ASAP ("shrink" buffer before passing
it to qstr_from_str_take()).
2014-01-13 23:31:06 +02:00
..
2014-01-11 00:58:59 +00:00
2014-01-12 00:20:49 +02:00
2014-01-04 18:44:46 +00:00
2014-01-12 19:16:59 +00:00
2014-01-12 19:16:59 +00:00
2014-01-11 00:58:59 +00:00
2014-01-12 23:37:45 +00:00
2014-01-12 22:04:21 +02:00
2014-01-05 12:08:55 -08:00
2014-01-11 00:58:59 +00:00