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

Avoid mutable global atom in core namespace #2

Open
paul-english opened this issue Nov 3, 2014 · 0 comments
Open

Avoid mutable global atom in core namespace #2

paul-english opened this issue Nov 3, 2014 · 0 comments

Comments

@paul-english
Copy link
Owner

I ported this library from an earlier scheme library which made use of a global var e. This is used as a counter in forward-mode and reverse-mode. This can be refactored so that the state isn't global and works with concurrent code.

It should require passing the state locally when calling a function that uses forward or reverse mode.
@paul-english paul-english changed the title Avoid mutable global atom in main namespace Avoid mutable global atom in core namespace Nov 3, 2014
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
1 participant
@paul-english