Skip to content

Improve Range and Reverse #204

Description

@SeanTAllen

A decent amount of conversation came up on #201 about the "bad API" and footgun nature of using Range to descend rather than ascend and about how Range and Reverse could be improved to work together for providing ascending and descending.

We'd love to see someone take up designing such changes and writing the RFC.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions