Segsource is a crate designed to assist in reading data. Although is specifically designed with
binary (u8) data, it is not limited to this.
Overview
Segsource is designed to easily and efficiently allow the reading of data without using much
memory. It does this by having two basic concepts: [Source]s, which own the data and
[Segment]s which allow access the data.
Each [Segment] is a thread-safe struct that retains minimal basic information such as the
position of an internal cursor (expressed via the [Segment::current_offset] method), a
reference to this data, etcetera.
Feature Flags
The following features are available for segsource:
asyncwhich adds support for variousasyncoperations usingtokio.derivewhich includes several macros for creating structs from [Segment]s.mmapwhich adds support for memory mapped files.stdwhich adds support for file and I/O operations.with_byteswhich adds support for using thebytescrate.
Of these, only derive and std are enabled by default.
Why segsource?
There are various other crates out there in a similar vein to segsource, and in your use case, some of them might be a better idea. I'll go through a few of the other options and let you decide for yourself:
-
bytes:segsourceactually offers native support forbytescrate via the appropriately namedbytesfeature. While bytes is great, it does have its limitations, the two biggest ones being the most read operations require it to be mutable and that there's no way to go "back". Segsource solves both of these cases. -
binread: Not a replacement forsegsourceas a whole, but for the derivations provided via thederivefeature. As of this writing,binreadis more feature rich thansegsource's derives (and since [Segment]s extendstd::io::Seekandstd::io::Read, they will work withbinread]. Unfortunately, this again requires the passed in -
bitvec: You may have noticed that you can essentially do simple memory emulation withsegsource (e.g. you can have an initial offset, you work in offsets, etcetera). Simple, being the keyword here.bitvec` is not simple nor can it be given its scope. -
std: You could use various items from the standard library, such as aVecor anio::Cursor, but all of these have limitations (e.g. aVeccan't have an initial offset and a can only move relative to its current position).
Derive
Documentation is on my TODO list...
Offsets
Instead of indexes, segsource use offsets. Depending on your use case, these will probably end up being the same. However, you can specify an initial offset that will essentially change the index from zero to whatever the initial_offset is.
For example:
# use ;
# type SourceOfYourChoice = ;
let test_data = ;
let source = from_u8_slice_with_offset.
unwrap;
let segment = source.all.unwrap;
assert_eq!;
Validation
One thing you may have noticed is that we had to unwrap the value each time. This is because methods first check to make an offset is valid. For example:
# use ;
# type SourceOfYourChoice = ;
# let test_data = ;
# let source = from_u8_slice_with_offset.
# unwrap;
# let segment = source.all.unwrap;
assert!;