-
-
Currently, the command exit with code 1 when file is not formatted and the output of the command differs from the initial content of the module.
However, I would expect it to succeed even if file i…
-
This is the reason for
- #24.
It also makes errors spanning several lines highlight incorrectly.
-
Based on the origin of the issue:
- https://github.com/anoma/juvix/issues/2114
We currently exclude files in the "tests" folder from being formatted, as some of them are expected to not pass the p…
-
I compiled the Hanoi example with the `--debug` flag for the native target on macOS aarch64:
https://github.com/anoma/juvix/blob/dbe9ff61d794637a3315068c65bfd296512f07dc/examples/milestone/Hanoi/Ha…
-
The runtime crash can be reproduced with the merge sort and fibonacci bench tests:
https://github.com/anoma/juvix/blob/8d7e669f7499b4122d9b1a9baf42828d1c163c7a/tests/benchmark/mergesort/juvix/merge…
-
This makes it impossible e.g. to launch the REPL in the home directory on MacOS because of permission issues. And it's unnecessary.
We should also consider disabling the directory traversal when co…
-
Implement a direct translation of JuvixCore to VampIR.
It can be assumed that we're translating a single main function of type `Int -> ... -> Int -> Int` which has the form `\x1 ... \xn -> b` where…
-
See the attached image. The first three dashes (-) in the third comment line are black and non-italic.
![image](https://user-images.githubusercontent.com/62751/209225902-7cba0eb0-43ed-4119-ac33-c94…
-
Say you have the following module:
Foo.juvix
```
--- Some comment
--- Other comment
module Foo;
```
When you run:
```
juvix --no-colors dev scope --with-comments Foo.juvix
```
The o…