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

Evaluation and Reduction with environment should use a Map instead of a List to represent the Environment #53

Closed
GoogleCodeExporter opened this issue Jun 21, 2015 · 2 comments
Closed

Evaluation and Reduction with environment should use a Map instead of a List to represent the Environment #53

GoogleCodeExporter opened this issue Jun 21, 2015 · 2 comments
Labels
auto-migrated Milestone-Release2.0.2 Priority-Medium Type-Other

Comments

@GoogleCodeExporter
Copy link 

This is another breaking change in this part of the API, but in the long run is 
the right choice and being a new feature as of version 2.0.0 we can consider 
these "experimental" parts of the API.

This does not affect the unit testing Assertion API.

Original issue reported on code.google.com by stephen....@gmail.com on 13 Jul 2011 at 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-Release2.0.2 Priority-Medium Type-Other
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter