Parser: Decouple Topologies and generic types from hardcoded strings
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 61
Description
parse_topology is heavily hardcoded to expect specific strings like "Host", "NPU", "AccCore". If we want to support dynamic, user-defined topologies or read topologies from a target specification file, the parser needs to treat topologies as resolved symbols.
Similarly, Tensor is hardcoded as a special case in parse_type.
Tasks:
- Remove hardcoded matches for Topologies and Tensors.
- Implement standard generic type parsing for types like
Tensor<T, ...>and rely on semantic analysis to validate topology and memory markers.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the parse_topology and parse_type entry points in the Rust parser, then trace how semantic analysis resolves symbols and validates topology and memory markers. Replace the hardcoded topology and Tensor cases with generic parsing, and confirm that user-defined topologies and types such as Tensor<T, ...> are accepted while validation remains semantic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100