Documentation says to call vector:set with nil if you don't want the underlying x or y to be changed.
However, doing that ends up triggering LSP diagnostic message:
Diagnostics:
1. Cannot assign `nil` to parameter `number`.
- `nil` cannot match `number`
- Type `nil` cannot match `number` [param-type-mismatch]
Documentation says to call
vector:setwithnilif you don't want the underlyingxoryto be changed.However, doing that ends up triggering LSP diagnostic message: