Add ability for the analyzer to recognize const fields (#2774)

This means the value of the fields is tracked as a const value instead of a field reference.
This is to support some additional code patterns as well as align the behavior with the linker. Compiler will inline the const fields into the IL effectively removing the field refernce in these cases and linker only sees the constant. So ideally the analyzer should have a similar behavior.

1 files changed, 16 insertions, 1 deletions

diff --git a/test/Mono.Linker.Tests.Cases/DataFlow/GetTypeDataFlow.cs b/test/Mono.Linker.Tests.Cases/DataFlow/GetTypeDataFlow.cs
index dff625716..ef58eac31 100644
--- a/test/Mono.Linker.Tests.Cases/DataFlow/GetTypeDataFlow.cs
+++ b/test/Mono.Linker.Tests.Cases/DataFlow/GetTypeDataFlow.cs
@@ -34,6 +34,7 @@ namespace Mono.Linker.Tests.Cases.DataFlow
 			TestStringEmpty ();
 
 			TypeWithWarnings.Test ();
+			OverConstTypeName.Test ();
 
 			// TODO:
 			// Test multi-value returns
@@ -163,7 +164,6 @@ namespace Mono.Linker.Tests.Cases.DataFlow
 
 		class TypeWithWarnings
 		{
-
 			[RequiresUnreferencedCode ("--Method1--")]
 			public void Method1 () { }
 
@@ -179,6 +179,21 @@ namespace Mono.Linker.Tests.Cases.DataFlow
 			}
 		}
 
+		class OverConstTypeName
+		{
+			private const string s_ConstTypeName = "Mono.Linker.Tests.Cases.DataFlow." + nameof (GetTypeDataFlow) + "+" + nameof (OverConstTypeName);
+
+			[RequiresUnreferencedCode ("--Method1--")]
+			public void Method1 () { }
+
+			// https://github.com/dotnet/linker/issues/2273
+			[ExpectedWarning ("IL2026", "--Method1--", ProducedBy = ProducedBy.Trimmer)]
+			public static void Test ()
+			{
+				Type.GetType (s_ConstTypeName).RequiresPublicMethods ();
+			}
+		}
+
 		[return: DynamicallyAccessedMembers (DynamicallyAccessedMemberTypes.PublicParameterlessConstructor)]
 		private static string GetStringTypeWithPublicParameterlessConstructor ()
 		{