This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
[WIP] Migrate to advanced IPLD data structures #27
Conversation
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
|
closing for archival |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We’ve been working on standardized interfaces for advanced data structures in the IPLD project. A lot of the motivation behind them is make things like unixfs more resilient and future-proof.
I just migrated the current JS implementation to these interfaces and it’s been a massive improvement.
This starts to bring the spec up to date with these changes. But, we shouldn’t merge this until the terminology has solidified a bit. We’re currently talking about changing the name for a 4th time, and the rest of the related terminology is also still in flux.