Skip to content

Future API changes #56

@ljedrz

Description

@ljedrz

With the latest PR I've noticed one potential improvement that is unlikely to ever be truly needed, but would make the library more airtight; unfortunately it would break the API, so it will need to wait for a 4.0 release. Therefore, I'm opening this issue to list any such potential future changes, and I'll be collecting them into a dedicated branch.

Breaking changes (a checkmark indicates that the 4.0 branch already contains the item):

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions