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
I'm maybe wrong here and this is expected behavior, but when I load a byte from a slice with the indices [2..10] from a parent array, I get the bits [0..8] back.
I know this probably has something to do with the Msb0 ordering of the Bitslice. But I don't understand how it mangles a slice that is exactly the size of a byte that much.
It is putting the bits from the second byte it finds first, then puts the bits from the first bind behind them.
How can I just get the slice and make an u8 from it, regardless of what the byte boundaries of the parent array are?
The text was updated successfully, but these errors were encountered:
Schievel1
added a commit
to Schievel1/mview
that referenced
this issue
Mar 9, 2023
when the bytes were not read from byte boundaries in the buff but from
across them.
See also: ferrilab/bitvec#219
Signed-off-by: Pascal Jäger <pascal.jaeger@leimstift.de>
Hello,
I'm maybe wrong here and this is expected behavior, but when I load a byte from a slice with the indices [2..10] from a parent array, I get the bits [0..8] back.
e.g.:
Output:
I know this probably has something to do with the Msb0 ordering of the Bitslice. But I don't understand how it mangles a slice that is exactly the size of a byte that much.
It is putting the bits from the second byte it finds first, then puts the bits from the first bind behind them.
How can I just get the slice and make an u8 from it, regardless of what the byte boundaries of the parent array are?
The text was updated successfully, but these errors were encountered: