Tracking issue for Qei trait

Open
#362 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
embedded-iot

Research direction

Start by reviewing the 0.2.7 Qei documentation and source linked in the issue, then read the context in #357 and #51. Identify the unresolved breaking problems and current use cases before proposing a design. Done means the Qei trait is restored with its associated types bounded appropriately for generic code.

Written by the indexing model from the issue text.

Description

The Qei trait available on the 0.2.x versions has been removed ahead of the 1.0.0 release. See: #357
This issue servers as a tracking issue until we add it back. The open (breaking) problems should be reasonably-well solved and all associated types should have appropriate bounds that enable generic code use.

Timer traits as of the 0.2.7 release:

Relevant issues/PRs:

  • #51
  • Your issue here!

Please feel free to participate, highlight your current use cases, problems and provide solutions.

Dominant language
Rust
Stars
2.7k
Forks
282
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-embedded/embedded-hal

All issues in rust-embedded/embedded-hal

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.