Self-documenting `Input` type parameter subtrait
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
As [commented][1] by @rlidwka:
> _It is a bit unfortunate that Input is not self-documenting, ideally we'd have `Input` instead of `Input`, and users could've just looked up which types implement `InputType` trait. [...]_
Technically that would be an API breaking change, but I don't know whether users ever implemented custom input types.
[1]: https://github.com/bevyengine/bevy/pull/10825#issuecomment-1837260997
Contributor guide
Research direction
The issue does not name a file or test. Start by reviewing the referenced PR discussion and locating the Input definition and its current bounds; then assess the proposed InputType subtrait against the public API. Done means the intended self-documenting bound is implemented and its API-breaking impact is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100