juvix/tests/positive/Literals.juvix

module Literals;

import Stdlib.Prelude open;

a : Int := 12313;

b : Int := -8;

c : Int := 10;

-+-- : Int := c + c;

d : String := "hellooooo";
add integer and string literals 2022-03-15 14:37:33 +03:00			`module Literals;`

Migrate old named application syntax (#2876) - Closes #2668 This pr migrates the old named application syntax to the new one. In order to migrate a juvix file to the new syntax it suffices to run the formatter. After the next release, we should completely remove the support for the old syntax. ## Other changes I've improved Scope negative tests. Previously, when a negative test failed, you could only see the title of the test and the message "Incorrect Error", as well as the Haskell file and line where the test is defined. This is extremely incovenient because you have to go to the haskell test file, go to the line where the error is defined, look at the name of the file and then visit that file. Moreover, you need to manually run the scoper on that file to see the error that was returned. I've fixed that and it now shows all relevant information. Example: ![image](https://github.com/anoma/juvix/assets/5511599/f0b7ec60-55dc-4f38-9b51-1fbedbda63f4) I've implemented this only using the `Generic` instance for the `ScoperError` type, so doing something similar for the rest of negative tests should be straightforward. 2024-07-12 19:31:09 +03:00			`import Stdlib.Prelude open;`
add integer and string literals 2022-03-15 14:37:33 +03:00
Format juvix files using new function syntax (#2245) 2023-07-11 18:22:07 +03:00			`a : Int := 12313;`
[test] improve test for literals 2022-03-16 14:42:06 +03:00
Format juvix files using new function syntax (#2245) 2023-07-11 18:22:07 +03:00			`b : Int := -8;`
[test] improve test for literals 2022-03-16 14:42:06 +03:00
Migrate old named application syntax (#2876) - Closes #2668 This pr migrates the old named application syntax to the new one. In order to migrate a juvix file to the new syntax it suffices to run the formatter. After the next release, we should completely remove the support for the old syntax. ## Other changes I've improved Scope negative tests. Previously, when a negative test failed, you could only see the title of the test and the message "Incorrect Error", as well as the Haskell file and line where the test is defined. This is extremely incovenient because you have to go to the haskell test file, go to the line where the error is defined, look at the name of the file and then visit that file. Moreover, you need to manually run the scoper on that file to see the error that was returned. I've fixed that and it now shows all relevant information. Example: ![image](https://github.com/anoma/juvix/assets/5511599/f0b7ec60-55dc-4f38-9b51-1fbedbda63f4) I've implemented this only using the `Generic` instance for the `ScoperError` type, so doing something similar for the rest of negative tests should be straightforward. 2024-07-12 19:31:09 +03:00			`c : Int := 10;`
[test] improve test for literals 2022-03-16 14:42:06 +03:00
Migrate old named application syntax (#2876) - Closes #2668 This pr migrates the old named application syntax to the new one. In order to migrate a juvix file to the new syntax it suffices to run the formatter. After the next release, we should completely remove the support for the old syntax. ## Other changes I've improved Scope negative tests. Previously, when a negative test failed, you could only see the title of the test and the message "Incorrect Error", as well as the Haskell file and line where the test is defined. This is extremely incovenient because you have to go to the haskell test file, go to the line where the error is defined, look at the name of the file and then visit that file. Moreover, you need to manually run the scoper on that file to see the error that was returned. I've fixed that and it now shows all relevant information. Example: ![image](https://github.com/anoma/juvix/assets/5511599/f0b7ec60-55dc-4f38-9b51-1fbedbda63f4) I've implemented this only using the `Generic` instance for the `ScoperError` type, so doing something similar for the rest of negative tests should be straightforward. 2024-07-12 19:31:09 +03:00			`-+-- : Int := c + c;`
Add `juvix format` command (#1886) This PR adds `juvix format` that can be used to format either a single Juvix file or all files in a Juvix project. ## Usage ``` $ juvix format --help Usage: juvix format JUVIX_FILE_OR_PROJECT [--check] [--in-place] Format a Juvix file or Juvix project When the command is run with an unformatted file it prints the reformatted source to standard output. When the command is run with a project directory it prints a list of unformatted files in the project. Available options: JUVIX_FILE_OR_PROJECT Path to a .juvix file or to a directory containing a Juvix project. --check Do not print reformatted sources or unformatted file paths to standard output. --in-place Do not print reformatted sources to standard output. Overwrite the target's contents with the formatted version if the formatted version differs from the original content. -h,--help Show this help text ``` ## Location of main implementation The implementation is split into two components: * The src API: `format` and `formatProject` https://github.com/anoma/juvix/blob/73952ba15c90f33919c75426cf62ae7e83fd3225/src/Juvix/Formatter.hs * The CLI interface: https://github.com/anoma/juvix/blob/73952ba15c90f33919c75426cf62ae7e83fd3225/app/Commands/Format.hs ## in-place uses polysemy Resource effect The `--in-place` option makes a backup of the target file and restores it if there's an error during processing to avoid data loss. The implementation of this uses the polysemy [Resource effect](https://hackage.haskell.org/package/polysemy-1.9.0.0/docs/Polysemy-Resource.html). The recommended way to interpret the resource effect is to use `resourceToIOFinal` which makes it necessary to change the effects interpretation in main to use `Final IO`: https://github.com/anoma/juvix/blob/73952ba15c90f33919c75426cf62ae7e83fd3225/app/Main.hs#L15 ## Format input is `FilePath` The format options uses `FilePath` instead of `AppFile f` for the input file/directory used by other commands. This is because we cannot determine if the input string is a file or directory in the CLI parser (we require IO). I discussed some ideas with @janmasrovira on how to improve this in a way that would also solve other issues with CLI input file/parsing but I want to defer this to a separate PR as this one is already quite large. One consequence of Format using `FilePath` as the input option is that the code that changes the working directory to the root of the project containing the CLI input file is changed to work with `FilePath`: https://github.com/anoma/juvix/blob/f715ef6a531f63c40ac3f629dd9cfea7e867507a/app/TopCommand/Options.hs#L33 ## New dependencies This PR adds new dependencies on `temporary` and `polysemy-zoo`. `temporary` is used for `emptySystemTempFile` in the implementation of the TempFile interpreter for IO: https://github.com/anoma/juvix/blob/73952ba15c90f33919c75426cf62ae7e83fd3225/src/Juvix/Data/Effect/Files/IO.hs#L49 `polysemy-zoo` is used for the `Fresh` effect and `absorbMonadThrow` in the implementation of the pure TempFile interpreter: https://github.com/anoma/juvix/blob/73952ba15c90f33919c75426cf62ae7e83fd3225/src/Juvix/Data/Effect/Files/Pure.hs#L91 NB: The pure TempFile interpreter is not used, but it seemed a good idea to include it while it's fresh in my mind. * Closes https://github.com/anoma/juvix/issues/1777 --------- Co-authored-by: Jonathan Cubides <jonathan.cubides@uib.no> 2023-03-29 16:51:04 +03:00
Migrate old named application syntax (#2876) - Closes #2668 This pr migrates the old named application syntax to the new one. In order to migrate a juvix file to the new syntax it suffices to run the formatter. After the next release, we should completely remove the support for the old syntax. ## Other changes I've improved Scope negative tests. Previously, when a negative test failed, you could only see the title of the test and the message "Incorrect Error", as well as the Haskell file and line where the test is defined. This is extremely incovenient because you have to go to the haskell test file, go to the line where the error is defined, look at the name of the file and then visit that file. Moreover, you need to manually run the scoper on that file to see the error that was returned. I've fixed that and it now shows all relevant information. Example: ![image](https://github.com/anoma/juvix/assets/5511599/f0b7ec60-55dc-4f38-9b51-1fbedbda63f4) I've implemented this only using the `Generic` instance for the `ScoperError` type, so doing something similar for the rest of negative tests should be straightforward. 2024-07-12 19:31:09 +03:00			`d : String := "hellooooo";`