-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#67 Functions for unpacking based on byte arrays #71
Merged
Adhara3
merged 14 commits into
EFeru:main
from
Uight:Functions-for-unpacking-based-on-byte-arrays
Aug 27, 2024
Merged
Changes from 1 commit
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
d917d87
First version of a fast Unpack function based on using byte array
Uight d85870d
Do all unpacking based on ulong
Uight 53befe7
Improve Speed of array copy and reverse
Uight 07fa652
Remove apply limit method because its unclear how to implement it
Uight 0491476
Prepare WriteBitsFunctions usable for Packing signals based on byte[]
Uight 70eb9e6
Use c# datatypes and first version for txPack based on byte array
Uight 24fb54c
Ignore rider files
Uight 3bb40c7
Use datatype compatible to c++ code; Fix StartbitLE being maxed at 255
Uight fff3073
#67 Added a more complex unittest for big endian packing and added a …
Uight 017645e
Quick safe for benchmarks
Uight 6fbddbb
Add unpack benchmarks
Uight 1b7bad8
Remove ref when packing
Uight 614a69a
add byte packing testcases to existing testcases
Uight a062289
Add byte packing tests for lengths != 8
Uight File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part is bittersweet. It's easy and readable but allocating to just read backward it's a pity.
Maybe if we change the
ExtractBits
signature into something likewe could keep the same iteration without assuming that length is the limit. Just food for thoughts.
...or... (this is a bit outside the scope of this PR, but worth mentioning)
Today the
Packer
is a static class so it needs Signal and message info. If we optimize theSignal
class (or if we adda a sort of.GetReader()
on it) then we could optimize some stuff, removing ifs, and give a forward/backward reader depending on endianness