Skip to content

apply same fix to btree_generic.go? #60

Open
@glycerine

Description

@glycerine

I notice a recent fix applied to btree.go:

aeba20f

If it is correct, is there any reason not to do the same fix to btree_generic.go ?

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