Provide hints to deduce type from varname?

[eigenbom]

Just a thought about type inference...

Sometimes it feels redundant to annotate the type for a function when it might seem obvious. I wonder if, in a system like this, a user could supply type "matchers" or "hints" to let the type inference system have a better guess about an unannotated type.

In this example a new keyword "typematcher" might tell the system that a parameter named "circ" or "circle" may be of type "circle".

---@class circle
---@field radius number

---@typematcher circle "circ|circle"

local function get_area(circ)
  -- circ is deduced as type any|circle (equiv to ---@param circ circle|any)
  return 2 * math.pi * circ.radius * circ.radius
end

Another example ...

---@alias vec3 {x:number, y:number, z:number}

---@typematcher "v[0-9]" vec3

local function vec_add(v1, v2)
	return {v1.x + v2.x, ... } --[[@as vec3]]
end

[Papipo]

I think that the first example could yield false positives. I recommend to avoid magic stuff as much as possible and instead be explicit.
Second case, how many vecX types do you have? I would guess that vec2 and vec3 are probably the only ones you'll ever need. Just be explicit and define them.

My 2 cents.

[C3pa]

I am sure you could implement that using plugins.