rust-embedded / rust-embedded/cortex-m
DWT: differentiate the first comparator
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 202
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 2
Description
As discussed in #364 we should ideally check whether a DWT feature is supported statically. This is only realistically applicable for cycle count comparisons (but still requires a runtime check) which is only supported on the first comparator. An implementation would then have some DWTComparatorFirst and DWTComparator structures that implement a common trait: if cycle count comparison is configured for DWTComparator, an error is returned.
Opening this issue for discussion purposes for now. At present the documentation warns that cycle count comparison is only available with the first comparator.
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 reading the discussion in #364 and the current DWT documentation describing cycle-count comparison. Clarify the proposed distinction between first and later comparators, including the common trait and runtime check. Done means the API design is agreed and cycle-count configuration on a non-first comparator is rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100