Asger F
Asger F
Use this issue to track general modular compilation concerns. This is very incomplete, but the general plan so far is this: The binary format currently uses symbolic references, which generally...
The translation from analyzer to kernel generates an `InvalidStatement` or `InvalidExpression` when we can detect at compile-time that a runtime error should be thrown. This statement throws at runtime, but...
No source information is currently preserved. My idea so far is to associate a breakpoint ID with every expression/statement where the debugger could conceivably stop, and a side table will...
When compiled for strong mode: - Inferred types must be made explicit - Checks must be made explicit The current analyzer-based frontend inserts inferred types, but not the necessary checks.
The text format is a one-way serialization, useful for diagnostics. We should be able to parse the text format back in so it can be used for writing test cases.
### Targeting a feature branch This PR is targeting a branch named `js/shared-dataflow-branch`, not `main` as we normally would. - Merging into `main` will happen at a later point, and...
Based on [this PR](https://github.com/github/codeql/pull/15386). Contains a prototype instantiation of Ruby.
There was a bug in the design of `TypeModel`, that meant when pruning models we have no way of knowing which types might be contributed via a `TypeModel`. This PR...
(Targeting `js/shared-dataflow-branch`) This greatly improves our ability to handle spread arguments and rest parameters, as well as `.apply()` calls and the `arguments` array. The basic idea is that each call...