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

Integrate a purity analysis tool to determine which methods to visit #100

Open
GoogleCodeExporter opened this issue Mar 4, 2015 · 0 comments
Open

Integrate a purity analysis tool to determine which methods to visit #100

GoogleCodeExporter opened this issue Mar 4, 2015 · 0 comments
Labels
auto-migrated Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Right now, Celeriac can either use auto-generated methods and methods marked as 
pure. Alternatively, the user can supply a list of methods to visit. The former 
misses a lot of methods, and the latter is tedious and error prone.

One tool that might work is Seal (Side effect analysis for .NET): 
https://seal.codeplex.com/

Original issue reported on code.google.com by Todd.Sch...@gmail.com on 8 Jun 2013 at 5:04
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 Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter