If we do #43710, the first thing you'll see every time you request completions on a string is a bunch of crossed-out properties. Ideally, we never would've shown these properties anyway, but we traditionally had to have them there because ES6.

Originally posted by @DanielRosenwasser in microsoft/TypeScript#43710 (comment)

__

@deprecated has its o

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

After ethereum/solidity#10737 we should be able to replace nearly all non-range-based for loops by range-based loops using appropriate ranges.

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