Closed MaksymZavershynskyi closed 3 years ago
Never liked cabbage, until I ate borsh.
Question is if this naming-indirection makes sense. I mean, reading technical docs and getting hungry, and guessing what this library does?
Possibly you should consider giving "borsh" a more expressive name, something that implies what this library does.
near-stream?
Never liked cabbage, until I ate borsh.
Question is if this naming-indirection makes sense. I mean, reading technical docs and getting hungry, and guessing what this library does?
Possibly you should consider giving "borsh" a more expressive name, something that implies what this library does.
near-stream?
Borsh name is too much ingrained into our codebase to be easily switched. Also, similar to CBOR, BORSH is a meaningful abbreviation see http://borsh.io/
Assigning to @kcole16 since the rest of the work is mostly on the Applayer side.
@nearmax I'm a bit lost given some work was already done - Are the steps left to finish this Epic required for MainNet or not?
This is not a Mainnet blocker. Since the remaining steps will not change the node API, we will be able to update via nearlib. Moving to the IceBox and removing from the Mainnet release.
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
I believe the majority of the work is done. The rest is tracked in #2242
#[derive(BorshSchema)]
. https://github.com/nearprotocol/borsh/pull/56