Always move initializer decompilation setting #3540
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Sometimes one needs to find out which options a dependency property has, what the coercion or changed methods are, or which types registers it. More often than not, DPs are initialized in a type with static constructor. In such case, the declaring type is not eligible for
beforeFieldInitand the decompiler cannot tell whether the static members have been initialized inline or in the constructor. However, It is non-trivial effort to manually find the constructor and the relevant initialization in it.Solution
This PR adds an option to always move initializers from static constructors to the declaration.
Before
After
Reference: https://github.com/dotnet/wpf/blob/main/src/Microsoft.DotNet.Wpf/src/PresentationFramework/System/Windows/Controls/TextBlock.cs