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

Evaluate cache dictionary in defining module #50

Merged
merged 2 commits into from
Feb 19, 2020

Conversation

kmsquire
Copy link
Member

@kmsquire kmsquire commented Feb 19, 2020

  • ... instead of Main.
  • Previously, it was defined in the Memoize module, which caused a
    warning to be issued.
  • It was changed to Main, which resolved the warning, but (still) did
    not allow custom dictionary types to be used.
  • This change still uses eval, but at least lets custom dictionary
    types to be used.

Fixes #33

* ... instead of Main.
* Previously, it was defined in the Memoize module, which caused a
  warning to be issued.
* It was changed to Main, which resolved the warning, but (still) did
  not allow custom dictionary types to be used.
* This change still uses `eval`, but at least lets custom dictionary
  types to be used.
@kmsquire kmsquire force-pushed the feature/allow-custom-dict-types branch from d595ef2 to f242345 Compare February 19, 2020 22:31
@kmsquire kmsquire merged commit 4355439 into master Feb 19, 2020
@kmsquire kmsquire deleted the feature/allow-custom-dict-types branch February 19, 2020 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot handle other associative types
1 participant