Better support for strongly typed generic commands
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.7k
- Forks
- 565
- PR merge metrics
- No merged PRs in 30d
Description
There is some previous discussion in #1004
Commands with concrete types (e.g., `Selector`) are nicely supported in druid, but commands with generic parameters (e.g. `Selector>`) are not, because the internal mechanism has no way to distinguish between `Selector>` and `Selector>`.
As discussed in #1004, the best current pattern is to use `Selector`, and then do the run-time type-checking yourself. It would be nice to have stronger compile-time safety.
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
Start by reading the issue and the previous discussion in #1004, then trace how druid distinguishes concrete command types. The desired outcome is stronger compile-time safety for generic commands without requiring Selector and manual runtime checks, but the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100