Timo
Timo
```js console.log(/.+a/.test('bba')); ``` This should return true, but currently returns false, because `.+` eagerly consumes the whole string. Instead it should work its way backwards and realize that `.+` should...
```js let f; function F() { this.a = 1; f = () => console.log(this); } new F(); f(); ``` should print `F { a: 1 }` but prints undefined
Currently dash tries to apply some optimizations at compile time, e.g. given ```js for (let i = 0; i < 1000; i++); ``` The comparison and increment get special opcodes...
When the other end disconnects, `TcpStream` will continue yielding empty `ArrayBuffer`s. This is probably wrong.
... when it should be treated as setting its internal prototype slot. E.g. ```js let b = { __proto__: null }; console.log(b.__proto__); // not null!! ```
A major problem with the current GC is that the vm has no way of telling that a variable in a native function is holding a reference to a JavaScript...
It might be worth in a lot of cases, especially for function calls. I'm guessing that an overwhelming number of function calls in any JS program usually only has up...
`std::any::TypeId` will be (is, on nightly) 128 bits, to mitigate collisions (iiuc). I'm not sure if this will have a perf impact (I've seen u128 be significantly slower than u64...
Fixes #12337 I split this PR up into two commits since this moves a method out of an `impl`, which makes for a pretty bad diff (the `&self` parameter is...
Closes #10754 Lint description should explain this PR, so I think there's nothing else to say here ^^ changelog: new lint: [`zombie_processes`]