ID 594763 - Blinkscript doesn't create the correct variable type when mixing float2 and int, depending on the order in which they are called while GPU acceleration is enabled.

Problem summary
Blinkscript doesn't create the correct variable type when mixing float2 and int, depending on the order in which they are called while GPU acceleration is enabled.
 
Customer reported version
Nuke 15.1v3
 
Customer reported platform
Windows 11
 
Steps to Reproduce
1) Download the attached Nuke script, then launch Nuke.
2) Open the downloaded Nuke script.
3) Double-click the Blinkscript7 node to view the Properties and kernel.
4) View the output of the Merge1(difference) node.
 
Expected behavior
There should be no difference from the Blinkscript filtering.
 
Actual behavior
When GPU acceleration is enabled for the Blinkscript7 node, the filtering of the Blinkscript is incorrect and displays a difference. This is due to line 24 in the script that shows the int position before the float variable.
 
Workaround
Swapping the position of the variable type (float2 versus int2) allows the Blinkscript to compile and display correctly.
 
Reproduced by Support in:
Nuke 15.1v5 - Windows 11, Rocky 9
Nuke 14.1v2/15.0v2 - Windows 11, Rocky 9 - regression
 
Unable to reproduce bug in:
 Nuke 14.1v1/15.0v1 - Windows 11, Rocky 9
 
Earliest version tested
14.1v1/15.0v1 - This feature (Mixing vector and scalar types) did not exist before these versions