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.

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

Materialization conflict #31

Open
lydia-duncan opened this issue Jan 15, 2015 · 0 comments
Open

Materialization conflict #31

lydia-duncan opened this issue Jan 15, 2015 · 0 comments

Comments

@lydia-duncan
Copy link
Member

When two modules that are used in a single program try to access
two separate external functions that share a name, the first function
accessed is used in both cases. I think that the materialization of
functions (and use of cached materializations) should take into
account the source location of the external function, so that
if the current source and the previous source differ, both will be
accessed under the correct circumstances.

See #30, test_materialization_conflict_[A|B].py

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

No branches or pull requests

1 participant