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

Test-Driven Code analysis #4

Open
JKamsker opened this issue Feb 4, 2020 · 0 comments
Open

Test-Driven Code analysis #4

JKamsker opened this issue Feb 4, 2020 · 0 comments

Comments

@JKamsker
Copy link

JKamsker commented Feb 4, 2020 •
edited
Loading

We all know that when using reflection, static analysis will/can fail.

What if the analyzer would run UnitTests in combination with a profiler?
That way ILStrip would know all possible execution paths and could perform its operations more efficient.
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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JKamsker