Skip to content

want a more bespoke container for PortRange #340

Description

@nicolaskagami

In #334 we introduced PortRange, which gives us guarantees around the type. However, there's still room to improve how we store and search these PortRanges. We could have a container that enforces and makes use of these properties (e.g non-overlapping ranges) for storing and retrieving these entries. We should definitely look at implementations such as RangeSet/RangeMap.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions