Skip to content
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

Necessary to re-export atomically? #8

Open
bbarker opened this issue Jan 23, 2019 · 1 comment
Open

Necessary to re-export atomically? #8

bbarker opened this issue Jan 23, 2019 · 1 comment

Comments

@bbarker
Copy link
Contributor

bbarker commented Jan 23, 2019

This seems to be brought in by prelude and classy-prelude (all I've tested), so was just curious why the re-export?
@agocorona
Copy link
Owner

Because the first version of tcache was from 2008! then atomically was not part of the prelude.
I take note to eliminate this export in the next version.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@agocorona @bbarker