Suggestion

🔍 Search Terms

• scanner + label:API
• SourceFileLike
• getPositionOfLineAndCharacter
• getLineAndCharacterOfPosition

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be impleme

https://github.com/less/less.js/blob/dc3a3105300930e2df14062fcf3de97d43db61b0/packages/less/src/less/tree/ruleset.js#L501
https://github.com/less/less.js/blob/dc3a3105300930e2df14062fcf3de97d43db61b0/packages/less/src/less/tree/debug-info.js#L1

Found this issue when trying to use less from the source. This works in dist because the class is compiled into a function.

### 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

This would increase readability in bigger tests, such as those in semanticTests/externalContracts.

// -- Double reserve
// account: 1
// reserve(string), 69 ether: 0x20, 3, "abc" ->
// owner(string): 0x20, 3, "abc" -> 0x1212121212121212121212121212120000000012
// account: 0
// -- Transfer
// setContent(string,bytes32): 0x40, 0, 3, "abc" ->
// transfer(string,address): 0x40, 555, 3

Adding a plain text to the header of a compiled and optimized .js-file may be useful for multiple reasons:

• Adding metadata like version, compiler settings, date, ...
• Adding execution information, e.g. #!/usr/bin/env node
• Adding a License, Author, Support info, URL, ...

Such a plain text header could easily be added to a .js in a postprocessing step after compilation. Howeve