-
I expect this example to have no error warnings.
-
The `example-checker.ipynb` has problems supressing type information. Instead of displaying `0.0`, it will display `np.float64(0.0)`. Part of the issue was to format arrays properly, but in doing so…
-
Store a union-find data structure in the type checker and `Eqn`
-
We've seen many problems in type-checker and many of them are scattered across different issues. If possible, it would be great if we can write those snippets at one place.
For those who aren't fa…
-
### Issue to be solved
Currently, the checker is implemented in a way where determining the type of an expression and other checks, like if an expression can be assigned to (which has e.g. the side-e…
-
```
~> go version
go version go1.22.4 darwin/amd64
~> make generate
==> removing autogenerated markdown...
find: website/pages: No such file or directory
==> removing autogenerated code...
P…
-
Example:
```
class Test {
public static void main(String[] args) {
int x = 0;
x = x * true;
}
}
```
javac gives:
```
Test.java:6: error: bad operand types for binary oper…
-
There should be no `eslint-ignore-next-line` or `@ts-expect-error` comments and the like in the code anywhere.
Maybe that's idealistic, but right now we have too many, some of which definitely hide…
-
When writing any kind of non-trivial Jack code, the complete lack of any type checking means both wasting time fixing silly errors and adding types that are effectively never used (except as documenta…
-
Anyone has had it problem?
I executed `weaver generate ./...`
Weaver version: v0.22.0 (binary/cli and go.mod)
Go version: v1.22
```panic: runtime error: invalid memory address or nil pointer der…