language

In strict mode (strict: true, inside a class or inside a module), duplicated property names get two errors instead of one:

// @strict: false
const first = { a: 1, a: 2 }
class C {
    m() {
        const second = { a: 1, a: 2 }
        return second.a
    }
}

Expected: one error on each a: 2.
Actual: two errors on the a: 2 inside the class:

1. Diagnostics.An_obje

When useing TamperMonkey or GreaseMonkey with less.js as a @require resource, sometimes there will be an error.
I trace the code found a small problem.
At https://github.com/less/less.js/blob/master/packages/less/src/less-browser/utils.js
function addDataAttrs param tag may be null, then the script will exec failed.
A short if may fix this, will you please add the code to check if tag is

There is the test/libsolidity/SolidityEndToEndTest.cpp file, which contains a lot of semantic tests. It is a large monolithic single C++ file, which takes a long time to compile and is hard to maintain.

We want to move as many test cases out to individual files under test/libsolidity/semanticTests. They should be grouped logically, by following the grouping in SolidityEndToEnd.

Have a

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

For now, Object protocol methods are (mostly) thin wrapper of matching vm functions. Because we don't need to have duplicated functions for same features, they need to be moved from vm to object protocol functions.

• vm path: vm/src/vm.rs
• object protocol path: vm/src/protocol/object.rs

The matching vm functions are easy to find because object methods are calling it.

• get_att

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).