FIX: ISXB-924 Fixed a variable name scope shadowing issue causing compilation problems on some Unity 2019 LTS. (#1953)

Author: ekcoh

Assets/Tests/InputSystem/CorePerformanceTests.cs

@@ -828,15 +828,15 @@ public void Performance_OptimizedControls_EvaluateStaleControlReadsWhenGamepadSt
 #endif
         return;
 
-        void MethodToMeasure(Gamepad gamepad)
+        void MethodToMeasure(Gamepad g)
         {
             var value2d = Vector2.zero;
 
             for (var i = 0; i < 1000; ++i)
             {
                 // Make sure state changes are different from previous state so that we mark the controls as
                 // stale.
-                InputSystem.QueueStateEvent(gamepad,
+                InputSystem.QueueStateEvent(g,
                     new GamepadState
                     {
                         leftStick = new Vector2(i / 1000f, i / 1000f),

Packages/com.unity.inputsystem/CHANGELOG.md

@@ -26,6 +26,7 @@ however, it has to be formatted properly to pass verification tests.
 - Fixed an issue where adding a `OnScreenStick` to a regular GameObject and entering play-mode would lead to exceptions being generated.
 - Fixed InputActionReference issues when domain reloads are disabled [ISXB-601](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-601), [ISXB-718](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-718), [ISXB-900](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-900)
 - Fixed a performance issue with many objects using multiple action maps [ISXB-573](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-573).
+- Fixed an variable scope shadowing issue causing compilation to fail on Unity 2019 LTS.
 
 ### Added
 - Added additional device information when logging the error due to exceeding the maximum number of events processed