bitio alternatives and similar packages
Based on the "Miscellaneous" category.
Alternatively, view bitio alternatives based on common mentions on social networks and blogs.
-
go-formatter
A curated list of awesome Go frameworks, libraries and software -
golang-standards/project-layout
Standard Go Project Layout -
archiver
Easily create & extract archives, and compress & decompress files of various formats -
ardanlabs/service
Starter code for writing web services in Go using Kubernetes. -
go-multierror
A Go (golang) package for representing a list of errors as a single error. -
go-restful-api
An idiomatic Go REST API starter kit (boilerplate) following the SOLID principles and Clean Architecture -
ghorg
Quickly clone an entire org/users repositories into one directory - Supports GitHub, GitLab, Bitbucket, and more 🥚 -
xstrings
Implements string functions widely used in other languages but absent in Go. -
go-shortid
Super short, fully unique, non-sequential and URL friendly Ids -
gountries
Gountries provides: Countries (ISO-3166-1), Country Subdivisions(ISO-3166-2), Currencies (ISO 4217), Geo Coordinates(ISO-6709) as well as translations, country borders and other stuff exposed as struct data. -
container
A lightweight yet powerful IoC dependency injection container for the Go programming language -
go-starter
An opinionated production-ready SQL-/Swagger-first RESTful JSON API written in Go, highly integrated with VSCode DevContainers by allaboutapps. -
golang-templates/seed
Go application GitHub repository template. -
countries
Countries - ISO-639, ISO-3166 countries codes with subdivisions and names, ISO-4217 currency designators, ITU-T E.164 IDD phone codes, countries capitals, UN M.49 codes, IANA ccTLD countries domains, IOC/NOC and FIFA codes, VERY VERY FAST, compatible with Databases/JSON/BSON/GOB/XML/CSV, Emoji countries flags and currencies support, Unicode CLDR. -
antch
Antch, a fast, powerful and extensible web crawling & scraping framework for Go
Collect and Analyze Billions of Data Points in Real Time
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of bitio or a related project?
Popular Comparisons
README
bitio
Package bitio
provides an optimized bit-level Reader
and Writer
for Go.
You can use Reader.ReadBits()
to read arbitrary number of bits from an io.Reader
and return it as an uint64
,
and Writer.WriteBits()
to write arbitrary number of bits of an uint64
value to an io.Writer
.
Both Reader
and Writer
also provide optimized methods for reading / writing
1 bit of information in the form of a bool
value: Reader.ReadBool()
and Writer.WriteBool()
.
These make this package ideal for compression algorithms that use Huffman coding for example,
where decision whether to step left or right in the Huffman tree is the most frequent operation.
Reader
and Writer
give a bit-level view of the underlying io.Reader
and io.Writer
, but they also
provide a byte-level view (io.Reader
and io.Writer
) at the same time. This means you can also use
the Reader.Read()
and Writer.Write()
methods to read and write slices of bytes. These will give
you best performance if the underlying io.Reader
and io.Writer
are aligned to a byte boundary
(else all the individual bytes are assembled from / spread to multiple bytes). You can ensure
byte boundary alignment by calling the Align()
method of Reader
and Writer
. As an extra,
io.ByteReader
and io.ByteWriter
are also implemented.
Bit order
The more general highest-bits-first order is used. So for example if the input provides the bytes 0x8f
and 0x55
:
HEXA 8 f 5 5
BINARY 1000 1111 0101 0101
aaaa bbbc ccdd dddd
Then ReadBits will return the following values:
r := NewReader(bytes.NewBuffer([]byte{0x8f, 0x55}))
a, err := r.ReadBits(4) // 1000 = 0x08
b, err := r.ReadBits(3) // 111 = 0x07
c, err := r.ReadBits(3) // 101 = 0x05
d, err := r.ReadBits(6) // 010101 = 0x15
Writing the above values would result in the same sequence of bytes:
b := &bytes.Buffer{}
w := NewWriter(b)
err := w.WriteBits(0x08, 4)
err = w.WriteBits(0x07, 3)
err = w.WriteBits(0x05, 3)
err = w.WriteBits(0x15, 6)
err = w.Close()
// b will hold the bytes: 0x8f and 0x55
Error handling
All ReadXXX()
and WriteXXX()
methods return an error which you are expected to handle.
For convenience, there are also matching TryReadXXX()
and TryWriteXXX()
methods
which do not return an error. Instead they store the (first) error in the
Reader.TryError
/ Writer.TryError
field which you can inspect later.
These TryXXX()
methods are a no-op if a TryError
has been encountered before,
so it's safe to call multiple TryXXX()
methods and defer the error checking.
For example:
r := NewReader(bytes.NewBuffer([]byte{0x8f, 0x55}))
a := r.TryReadBits(4) // 1000 = 0x08
b := r.TryReadBits(3) // 111 = 0x07
c := r.TryReadBits(3) // 101 = 0x05
d := r.TryReadBits(6) // 010101 = 0x15
if r.TryError != nil {
// Handle error
}
This allows you to easily convert the result of individual ReadBits()
, like this:
r := NewReader(bytes.NewBuffer([]byte{0x8f, 0x55}))
a := byte(r.TryReadBits(4)) // 1000 = 0x08
b := int32(r.TryReadBits(3)) // 111 = 0x07
c := int64(r.TryReadBits(3)) // 101 = 0x05
d := uint16(r.TryReadBits(6)) // 010101 = 0x15
if r.TryError != nil {
// Handle error
}
And similarly:
b := &bytes.Buffer{}
w := NewWriter(b)
w.TryWriteBits(0x08, 4)
w.TryWriteBits(0x07, 3)
w.TryWriteBits(0x05, 3)
w.TryWriteBits(0x15, 6)
if w.TryError != nil {
// Handle error
}
err = w.Close()
// b will hold the bytes: 0x8f and 0x55
Number of processed bits
For performance reasons, Reader
and Writer
do not keep track of the number of read or written bits.
If you happen to need the total number of processed bits, you may use the CountReader
and CountWriter
types
which have identical API to that of Reader
and Writer
, but they also maintain the number of processed bits
which you can query using the BitsCount
field.
LICENSE
Licensed under either of
- [Apache License, Version 2.0](LICENSE-APACHE)
- [GNU LESSER GENERAL PUBLIC LICENSE, Version 2.1](LICENSE-LGPL-v2.1)
at your option.
*Note that all licence references and agreements mentioned in the bitio README section above
are relevant to that project's source code only.