Incorrect readonly property warning when initialising table in new solver strict mode

[nothing1649]

As of version 0.651, creating a table with a key being a readonly property of another table warns about the property being readonly, despite it not actually being assigned to. This only appears to occur in the new solver, and can be worked around by casting the key to any type or assigning it later.

--!strict
type readonlyTable = {read id: number}
local t:readonlyTable = {id = 1}

local _:{number} = {[t.id] = 1} --Property id of table 'readonlyTable' is read-only
local _:{number} = {[t.id::number] = 1} --no type error

local arr:{number} = {}
arr[t.id] = 1 --no type error

[aatxe]

Thanks for the report, the fix for this will be in the 0.652 release!