Allow tracking of global/environment property reads#5038
Allow tracking of global/environment property reads#5038rainersigwald merged 2 commits intodotnet:masterfrom
Conversation
|
This effectively adds back in the property tracking work done back in August '19 (with merge resolutions). This was reverted because of a failed RPS run with (IMO) questionable results. Is it possible to get an RPS run before/after this change goes in (if accepted)? |
Just wrote this a few days back: #4997 (comment) For the OrchardCore case, you can repeat your measurements on master, your PR without property tracking, your PR with property tracking. |
|
Per @cdmihai, launched an experimental build to run VS perf tests with latest changes. It passed. |
Forgind
left a comment
There was a problem hiding this comment.
I didn't see you address Rainer's comment. Since it passed RPS, this otherwise looks good to me.
…otnet#4461)" (dotnet#4663)" This reverts commit faf5e5d. Fixing merge error in a comment. Fix another merge issue. Merge fix.
Property reassignments behave like before (on by default).
e981c55 to
6426e79
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Re-reverting this as a starting point for #3432 and #5015
…#4461)" (#4663)"
This reverts commit faf5e5d.