Skip to content

Consider replacing hashbrown use in core API #911

@kevinhartman

Description

@kevinhartman

What is the expected enhancement?

Currently, some structs from hashbrown are used in the core API (e.g. the mapping parameter of token_swapper). As a result, downstream libraries are required to use the same minor version of hashbrown, which has proven to be somewhat cumbersome.

Note that by switching to the standard lib equivalents, we may take some perf hit, but perhaps this is worth the UX improvement.

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