Update B512Type.ts #3287
Update B512Type.ts #3287
Conversation
Summary This PR updates the documentation for B512 to improve understanding and usability. The changes include: Renaming Bits512 to B512 to better align with the wider ecosystem. Adding documentation on how to form a B512 from two B256 instances. Improving examples to reflect more complex use cases. Release Notes In this release, we: Updated the documentation for B512 to enhance clarity and usability. Breaking Changes No breaking changes were introduced in this PR. ### Checklist - [ ] All changes are covered by tests (or not applicable) - [ ] All changes are documented (or not applicable) - [ ] I reviewed the entire PR myself (preferably, on GH UI) - [ ] I described all Breaking Changes (or there's none)
Namanedogawa
requested review from
digorithm,
arboleya,
Torres-ssf,
Dhaiwat10,
danielbate,
nedsalk,
petertonysmith94 and
maschad
as code owners
|
|
|
@Namanedogawa is attempting to deploy a commit to the Fuel Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
Hey @Namanedogawa, thanks for the contribution! We love to get submissions from the community, but we prefer first-time contributions to be more substantial. If you are excited to make a contribution, feel free to look through our open issues for ideas! Closing for now. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
|
@Namanedogawa your PR desription and the changes you actually made are not at all aligned. This PR does not solve the issue it is trying to solve. Nor do the changes make any sense. |
Summary
This PR updates the documentation for B512 to improve understanding and usability. The changes include:
Closes #3241
Renaming Bits512 to B512 to better align with the wider ecosystem. Adding documentation on how to form a B512 from two B256 instances. Improving examples to reflect more complex use cases. Release Notes
In this release, we:
Updated the documentation for B512 to enhance clarity and usability. Breaking Changes
No breaking changes were introduced in this PR.
Checklist