Getting this weird warning with the new type solver, I can work around it if I pass two Color3 arguments instead of one, but passing only one Color3 shouldn’t result in a type warning since there is an overload for that.
Would like to know if I am doing something wrong or it’s just the new type solver being funky.
This seems to be a bug, possibly related to v702.
In the New Luau Type Solver, overload resolution is now slightly more principled during type inference. Prior we would attempt to unify arguments with all of the possible overloads, which would often select an overload at random.
File a bug report in Bug Reports > Studio Bugs
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.