Repository navigation
Initial top-level roadmap design - #456
Conversation
stringhandler
left a comment
There was a problem hiding this comment.
In a16f374
I see some of the links are missing. Would it perhaps be better to create them as empty documents? I think that might be better than trying to find broken links in future.
Otherwise, happy
| |--------|---------------------------------------|---------------------------------------------------------------------|---------------|--------------|-----| | ||
| | MOD | [Module system](MOD.md) | Rust-2018-style mod1les, external crates, content-based identity | — | - | - | | ||
| | MOD-1 | Internal modules | `mod x;` loads `x.simf`; `use` only brings names into scope | — | Needs design | - | | ||
| | MOD-2 | External crates | Dependency crates identified by Merkle-style `CrateId` hash | MOD-1 | Needs design | - | |
There was a problem hiding this comment.
In a16f374
These potentially are also dependent on IR-2
There was a problem hiding this comment.
Sure, I put an IR-2 and changed IR-1 to depend on MOD-1 rather than MOD-2 so that we wouldn't have a circle.
I expect that we won't be able to get these dependencies exactly correct until we're into the weeds on these. Especially since some things need to be done concurrently.
FWIW I think we could do an initial version of MOD-2 which literally just hashes the file contents rather than any creative hash. This would be very limiting, but that's why we have MOD-3.
| | SYN-4 | `return` expressions | syntax sugar for "early returns" | — | Needs design | — | | ||
| | SYN-5 | Better loops | More conventional-looking, still statically bounded loops | - | Needs design | — | | ||
| | SYN-6 | Unbounded loops | Recursion, unbounded loops, general `disconnect` support? | - | Needs design | — | | ||
| | SYN-7 | Universal sighash | Better sighashing, language support for "universal sighash" | - | Needs design | — | |
There was a problem hiding this comment.
I don't think so. Though it may depend on the canonical CMR. I suspect this is a thing where we can theoretically implement the feature with no other dependencies, but it'll be extremely hard to use without more language features.
a16f374 to
103c5d1
Compare
|
Pushed to add a bunch of empty documents, and one of the missing dependencies that stringhandler suggested. |
103c5d1 to
962030e
Compare
|
I'd also like to see a feature that adds a |
|
I think let's merge this and then further comments can be PR's or issues |
This, for example, can be discussed and added in a follow up PR (discussion can be started on the forum) |
|
Yeah, I think this "cost" thing might make sense as an entry under the empty |
|
On 962030e successfully ran local tests |
This is a draft of the new
doc/roadmap/tree. It doesn't fill in any of the design documents for the actual features, just adds a list. Please mention if something you care about is not on here (or if something you hate is on here).My goal with this is just to get an exhaustive list and see if we're missing anything, and to organize to see what things are "unblocked" in the sense that we can start working on them without needing other design features in place.