Skip to content

uniqueName function may still have conflict names #7

Open
@Enzo-Liu

Description

@Enzo-Liu

I think the key in Names should not be the raw name. but the generated new name.
uniqueName function

Like follows in ghci

λ> let supply = Map.empty
λ> let (n1,supply1) = uniqueName "abc" supply
λ> let (n2,supply2) = uniqueName "abc" supply1
λ> let (n3,supply3) = uniqueName "abc1" supply2
λ> n3
"abc1"
λ> n2
"abc1"
λ> n1
"abc"

Just to make sure, this is not the wanted behavior, right?

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