New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

uniqueName function may still have conflict names #7

Open

Enzo-Liu opened this issue Feb 24, 2018 · 0 comments

Contributor

Enzo-Liu commented Feb 24, 2018

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?

The text was updated successfully, but these errors were encountered:

sdiehl closed this as completed

sdiehl reopened this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment