Suggestion

I suggest a better error message telling that arguments is a reserved keyword or something that cannot be used in TS in strict mode.

✅ Viability Checklist

According to documentation https://lesscss.org/functions/#color-definition-hsl
hsl() function should output a color, but it does not. rgb() and hsv() behave as documented.

$ npx lessc --version
lessc 4.1.1 (Less Compiler) [JavaScript]
$ cat problem.less 
.problem {
  color: rgb(128, 255, 0);
  background-color: hsl(90, 100%, 50%);
  border-color: hsv(90, 100%, 50%);
}
$ npx lessc pr

### Example
let unreachableProxy = "http://127.0.0.1:8888"
try:
  let client = newHttpClient(proxy=newProxy(unreachableProxy), timeout=1)
  var res = client.getContent("https://github.com")
  echo res
except:
  echo "Timed out"

Current Output

timeout variable is ignored, program stuck until default socket timeout will happen

Expected Output

Timed out a

Abstract

The compiler is pretty lax about command-line options whose values it does not use and just ignores many of them. It should report errors instead.

Over time we've started adding checks against this (e.g. #9075, #9364) they they're still very incomplete.

Motivation

Not getting an error when an option is invalid makes it harder for the user to realize that. It's especially pro

It would be useful to have a java.util.BitSet implementation. It looks like most Java collections are available but this one fell through the cracks (perhaps because it's not part of the Collection hierarchy).