-
Notifications
You must be signed in to change notification settings - Fork 41
Issues: near/borsh
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Deserialization fails if slice is longer then the length of the serialized data
P2
Priority 2
#27
opened Oct 17, 2019 by
jackcmay
Investigate safety of trait objects
P1
Priority 1
security
Security issues
#54
opened Feb 3, 2020 by
MaksymZavershynskyi
Set up testing with miri to catch undefined behavior bugs
CI
Continuous Integration
good first issue
Good for newcomers
housekeeping
Refactoring, cleanups, code quality
security
Security issues
testing
Unit testing / integration testing
#66
opened Mar 23, 2020 by
frol
JSON example of the new schema format
docs
rustdoc, nomicon, and docs.nearprotocol.com
P1
Priority 1
#71
opened Apr 30, 2020 by
MaksymZavershynskyi
Capacity allocation for vector deserialization
P2
Priority 2
#16
opened Sep 13, 2019 by
ilblackdragon
Rewrite New feature or request
BorshSchema
to use const functions
enhancement
#79
opened Jun 15, 2020 by
MaksymZavershynskyi
[Discussion] General workflow (common in all borsh implementations) of borsh
#83
opened Aug 4, 2020 by
ailisp
Improve borsh solidity, reduce gas use and increase performance by solidity assembly
#90
opened Aug 4, 2020 by
ailisp
Extend borsh-js, borsh-ts and borsh-rs to support schema based workflow
#92
opened Aug 4, 2020 by
ailisp
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.