Setting a float value in a table in a table using `vim.api.nvim_win_set_var` results in the inner table have values as a table with `true` and `false` as the indexes about neovim

[zeertzjq]

This behavior is necessary to distinguish a Float from a Number. In Lua these are the same type, while in RPC API and Vimscript they are different. See :h lua-special-tbl

                                                              *lua-special-tbl*
4. Table with `vim.type_idx` key may be a dictionary, a list or floating-point
   value:
   - `{[vim.type_idx]=vim.types.float, [vim.val_idx]=1}` is converted to
     a floating-point 1.0. Note that by default integral Lua numbers are
     converted to |Number|s, non-integral are converted to |Float|s. This
     variant allows integral |Float|s.
   - `{[vim.type_idx]=vim.types.dictionary}` is converted to an empty
     dictionary, `{[vim.type_idx]=vim.types.dictionary, [42]=1, a=2}` is
     converted to a dictionary `{'a': 42}`: non-string keys are ignored.
     Without `vim.type_idx` key tables with keys not fitting in 1., 2. or 3.
     are errors.
   - `{[vim.type_idx]=vim.types.array}` is converted to an empty list. As well
     as `{[vim.type_idx]=vim.types.array, [42]=1}`: integral keys that do not
     form a 1-step sequence from 1 to N are ignored, as well as all
     non-integral keys.

[zeertzjq]

row and col in nvim_win_get_config can only be Float. Vimscript variables can be either Integer or Float.

[wookayin]

Question: I recall #24430 had the similar issue before. If nvim 0.10 has changed (fixed) the behavior on nvim_win_{get,set}_config (see #27284), nvim_win_{get,set}_var should deserve the same fix, or shoudn't it? If not, what's special about nvim_win_{get,set}_config?