You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice to generalize what we have for jit diffs to handle cases where the framework (or some assembly) has changes. This is somewhat doable today, but clunky:
Though for corelib it is more involved as we currently can't load a different copy of corelib (perhaps solvable with assembly load contexts?).
Analysis may need tweaking since we will see more mismatches in methods. And we might want to publish overall per-assembly summary data.
Would also be nice if via reflection we could enumerate all instantiations of generics, so that the analysis also highlight refactoring that increases or reduces the net amount of instantiation needed. My understanding is that this is not possible today.
The text was updated successfully, but these errors were encountered:
Would be nice to generalize what we have for jit diffs to handle cases where the framework (or some assembly) has changes. This is somewhat doable today, but clunky:
Though for corelib it is more involved as we currently can't load a different copy of corelib (perhaps solvable with assembly load contexts?).
Analysis may need tweaking since we will see more mismatches in methods. And we might want to publish overall per-assembly summary data.
Would also be nice if via reflection we could enumerate all instantiations of generics, so that the analysis also highlight refactoring that increases or reduces the net amount of instantiation needed. My understanding is that this is not possible today.
The text was updated successfully, but these errors were encountered: