scylladb / scylladb/python-rs-driver
Switch protocol based policies to class based
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 7
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 9
Description
Description:
Currently, policy interfaces (such as HostFilter, etc.) are defined as typing.Protocol.
While protocols enable structural subtyping without explicit inheritance, they present limitations for future interface extensibility:
- Default implementations do not work with structural subtyping: If a default method is added to a Protocol, existing classes that implement the protocol implicitly (without directly inheriting from it) will not receive the default implementation.
- Breaking changes on interface extension: Adding new methods to a protocol breaks non-inheriting implementors.
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
No files or tests are named. Start by locating policy interfaces such as HostFilter and the classes that implement them, then trace how those policies are typed and used. Done means the policy interfaces are class-based while existing implementors retain their behavior and interface extensions can provide defaults without breaking them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100