Module Overloading
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
We can do module overloading at the Abstract Typing Level. That makes it such that modules can still be navigated reliably (so no C++-style parsing idiocy), while allowing for overloaded naming. Given that we don't intend to add traits, it means that with module overloads it isn't possible to dynamically "pick" an implementation based on template arguments. To me that seems like a fair tradeoff, since highly generic hardware development isn't a goal of SUS.
Synergises very well with #58, such that we can have operator overloading for other types, like float (See #27)
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, tests, or entry points are named. Start by reading related issues #58 and #27, then clarify the module-overloading design and navigation constraints. A concrete completion criterion would need to be agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100