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
I only tested this in VS Code, the latest version as of this date. I'm not sure when this became a bug, or whether it's always been this way.
To replicate the bug, create a procedure and then using the F2 command rename one of the parameters which happens to have the exact identifier as a field from any struct used in the procedure. This only replaces the token, and it doesn't rename the actual struct field in the struct definition.
Example:
Before renaming parameter 'x':
random_procedure :: proc(x, y: f32)
{
mouse.x += x
mouse.y += y
}
I only tested this in VS Code, the latest version as of this date. I'm not sure when this became a bug, or whether it's always been this way.
To replicate the bug, create a procedure and then using the F2 command rename one of the parameters which happens to have the exact identifier as a field from any struct used in the procedure. This only replaces the token, and it doesn't rename the actual struct field in the struct definition.
Example:
Before renaming parameter 'x':
After renaming parameter 'x' to 'offset_x':
It doesn't matter where the struct lives, if outside or inside the procedure scope.
The text was updated successfully, but these errors were encountered: