Don't error on unconnected ports
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
It's a sad reality that while developing modules, some of the ports will be unconnected. This prevents the compiler from giving good typechecking & latency counting info until all ports have been connected. This usually happens only right at the end of design. Perhaps, only reporting a warning and emitting randomly-chosen absolute latency values for such unconnected ports will ease development a bit.
(also, this is in line due to complaints about the unconnected ports errors being quite obtuse)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the compiler diagnostic for unconnected ports and the logic that computes typechecking and latency information. Done means unconnected ports produce warnings rather than errors, compilation continues with absolute latency values, and the resulting diagnostics are less obtuse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100