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
The reference to const kPlantableNameKey is replaced by its value in the constructor, which is valid code, but an unused assignment / variable warning at the IDE. Perhaps the decompiler could check for private constants and replace matching literals in scope, or perhaps this is a more specific edge case.
This is not a bug, but a request for improvement. While we do some prettifying of double and float constants, that can be expressed as fractions or multiples of Math.PI or E, I don't think this case is worth the effort.
Questions:
Where should we look for constants? Current type, current assembly or all referenced assemblies?
Should we look at possible sub strings?
These two questions are examples of why such a feature is problematic in my opinion.
Similar to #1084.
The reference to const
kPlantableNameKey
is replaced by its value in the constructor, which is valid code, but an unused assignment / variable warning at the IDE. Perhaps the decompiler could check for private constants and replace matching literals in scope, or perhaps this is a more specific edge case.Input code
Erroneous output (from .NET 8.0 SDK class library)
Details
The text was updated successfully, but these errors were encountered: