[p5.js 2.0+ Bug Report]: min/max function with variable length parametes

[TakagiHitoshi]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• WebGPU
• p5.strands
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

p5.js version

2.3.2

Web browser and version

chrome 150.0.7871.187

Operating system

Windows 11

Steps to reproduce this

This is not an exact bug report, but a request.
min function accepts variable length parameters in p5js v.1, Now it says "Expected at most 2 arguments, but received more in min()." Would be good if compatibility would be maintained.

Steps:

1. run a code with min(1, 2, 3, 4)

Snippet:

t=0
draw=_=>{
createCanvas(W=(w=200)2,W)+colorMode(HSB)+noFill()
for(R=0;R<w;R+=18)for(T=0;T<TAU;T+=.1)
translate(x=Rcos(U=T+t/41)+w,y=R*sin(U)+w),
rotate(t/R+U),
stroke(D=min(x,y,W-x,W-y)*2,w,w,9),
ellipse(0,0,D,D/2),
resetMatrix()
++t}

[xdroberto]

Hi @ksen0! I'd like to work on this one — could it be assigned to me?

I had a look at where the message comes from, in case it's useful. The runtime is already variadic and computes the right result: fn.max = function(...args) in src/math/calculation.js. The false warning comes from the arity the friendly error system derives from the JSDoc, which currently declares only two parameters (n0, n1), so anything beyond two arguments is reported as too many.

Worth noting that the documentation right above that function says "The version of max() with two or more parameters interprets them as individual numbers", and its own example is let m = max(10, 5, 20); — so the documented example currently triggers the warning.

There's already a precedent for the fix in the codebase: createVector uses @param {...Number} x for a rest parameter, and the validator handles rest params. So this looks like a JSDoc change on min() and max() rather than a change to the runtime or the validator.

One thing I'd like your input on before opening a PR: whether the signature should be {...Number} on its own, which would also allow max() with no arguments, or keep one required parameter followed by the rest. Happy to go with whichever you prefer.