juvix/app/Commands/Dev/Asm/Run.hs

module Commands.Dev.Asm.Run where

import AsmInterpreter
import Commands.Base
import Commands.Dev.Asm.Run.Options
import Juvix.Compiler.Asm.Translation.FromSource qualified as Asm

runCommand :: forall r. (Members '[Embed IO, App] r) => AsmRunOptions -> Sem r ()
runCommand opts = do
  afile :: Path Abs File <- fromAppPathFile file
  s <- readFile (toFilePath afile)
  case Asm.runParser (toFilePath afile) s of
    Left err -> exitJuvixError (JuvixError err)
    Right tab -> runAsm (not (opts ^. asmRunNoValidate)) tab
  where
    file :: AppPath File
    file = opts ^. asmRunInputFile
JuvixAsm (#1432) 2022-09-29 18:44:55 +03:00			`module Commands.Dev.Asm.Run where`

JuvixCore to JuvixAsm translation (#1665) An implementation of the translation from JuvixCore to JuvixAsm. After merging this PR, the only remaining step to complete the basic compilation pipeline (#1556) is the compilation of complex pattern matching (#1531). * Fixes several bugs in lambda-lifting. * Fixes several bugs in the RemoveTypeArgs transformation. * Fixes several bugs in the TopEtaExpand transformation. * Adds the ConvertBuiltinTypes transformation which converts the builtin bool inductive type to Core primitive bool. * Adds the `juvix dev core strip` command. * Adds the `juvix dev core asm` command. * Adds the `juvix dev core compile` command. * Adds two groups of tests: - JuvixCore to JuvixAsm translation: translate JuvixCore tests to JuvixAsm and run the results with the JuvixAsm interpreter, - JuvixCore compilation: compile JuvixCore tests to native code and WASM and execute the results. * Closes #1520 * Closes #1549 2023-01-09 20:21:30 +03:00			`import AsmInterpreter`
JuvixAsm (#1432) 2022-09-29 18:44:55 +03:00			`import Commands.Base`
			`import Commands.Dev.Asm.Run.Options`
			`import Juvix.Compiler.Asm.Translation.FromSource qualified as Asm`

Update CI to install Smoke, Github actions, and Makefile fixes (#1735) This PR adds some maintenance at different levels to the CI config, the Make file, and formatting. - Most of the actions used by the CI related to haskell, ormolu, hlint and pre-commit have been updated because Github requires NodeJS 16. This change removes all the old warnings related to nodeJs. In the case of ormolu, the new version makes us format some files that were not formatted before, similarly with hlint. - The CI has been updated to use the latest version of the Smoke testing framework, which introduced installation of the dependencies for Linux (libicu66) and macOS (icu4c) in the CI. In the case of macOS, the CI uses a binary for smoke. For Linux, we use stack to build smoke from the source. The source here is in a fork of [the official Smoke repo](https://github.com/SamirTalwar/smoke). Such includes some features/changes that are not yet in the official repo. - The Makefile runs the ormolu and hlint targets using as a path for the binaries the environment variables ORMOLU and HLINT. Thus, export those variables in your environment before running `make check,` `make format` or `make hlint`. Otherwise, the Makefile will use the binaries provided by `stack`. Co-authored-by: Paul Cadman <git@paulcadman.dev> 2023-01-24 13:50:23 +03:00			`runCommand :: forall r. (Members '[Embed IO, App] r) => AsmRunOptions -> Sem r ()`
JuvixAsm (#1432) 2022-09-29 18:44:55 +03:00			`runCommand opts = do`
Support more paths (#2000) - Closes #1993 This pr makes it possible to use `~`, `..` and environment variables in the `juvix.yaml` and all flags / input of the cli. In the CLI, the shell will be responsible for replacing environment variables with their value, so the usual syntax can be used. For the `dependencies` field, I have implemented a parser that has some restrictions: 1. Environment variables are given with the makefile-like syntax `$(VAR)` 2. The three characters `$` `(` `)` are reserved for the environment variables syntax. They cannot be part of the path. 3. `~` is reserved for `$(HOME)`. I.e. the prepath `~~` will expand to `$HOME$HOME`. 4. Nested environment variables are not allowed. Thanks @paulcadman for the feedback. I think we are ready to merge this nightmarish pr :ghost: --------- Co-authored-by: Paul Cadman <git@paulcadman.dev> 2023-04-19 17:56:48 +03:00			`afile :: Path Abs File <- fromAppPathFile file`
Use system locale independent readFile and writeFile APIs from with-utf8 (#2473) The problem with readFile and writeFile from text [Data.Text.IO](https://hackage.haskell.org/package/text-2.0.2/docs/Data-Text-IO.html) is that they use the system locale to determine the text encoding format. Our assumption is that all Juvix source files are UTF-8 encoded. I cannot reproduce the issue with using the old APIs on my machine, it can be reproduced on Arch linux. I'm not sure how to write a specific test for this. * Closes https://github.com/anoma/juvix/issues/2472 2023-10-26 11:13:33 +03:00			`s <- readFile (toFilePath afile)`
Support basic dependencies (#1622) 2022-12-20 15:05:40 +03:00			`case Asm.runParser (toFilePath afile) s of`
JuvixAsm (#1432) 2022-09-29 18:44:55 +03:00			`Left err -> exitJuvixError (JuvixError err)`
JuvixCore to JuvixAsm translation (#1665) An implementation of the translation from JuvixCore to JuvixAsm. After merging this PR, the only remaining step to complete the basic compilation pipeline (#1556) is the compilation of complex pattern matching (#1531). * Fixes several bugs in lambda-lifting. * Fixes several bugs in the RemoveTypeArgs transformation. * Fixes several bugs in the TopEtaExpand transformation. * Adds the ConvertBuiltinTypes transformation which converts the builtin bool inductive type to Core primitive bool. * Adds the `juvix dev core strip` command. * Adds the `juvix dev core asm` command. * Adds the `juvix dev core compile` command. * Adds two groups of tests: - JuvixCore to JuvixAsm translation: translate JuvixCore tests to JuvixAsm and run the results with the JuvixAsm interpreter, - JuvixCore compilation: compile JuvixCore tests to native code and WASM and execute the results. * Closes #1520 * Closes #1549 2023-01-09 20:21:30 +03:00			`Right tab -> runAsm (not (opts ^. asmRunNoValidate)) tab`
JuvixAsm (#1432) 2022-09-29 18:44:55 +03:00			`where`
Support more paths (#2000) - Closes #1993 This pr makes it possible to use `~`, `..` and environment variables in the `juvix.yaml` and all flags / input of the cli. In the CLI, the shell will be responsible for replacing environment variables with their value, so the usual syntax can be used. For the `dependencies` field, I have implemented a parser that has some restrictions: 1. Environment variables are given with the makefile-like syntax `$(VAR)` 2. The three characters `$` `(` `)` are reserved for the environment variables syntax. They cannot be part of the path. 3. `~` is reserved for `$(HOME)`. I.e. the prepath `~~` will expand to `$HOME$HOME`. 4. Nested environment variables are not allowed. Thanks @paulcadman for the feedback. I think we are ready to merge this nightmarish pr :ghost: --------- Co-authored-by: Paul Cadman <git@paulcadman.dev> 2023-04-19 17:56:48 +03:00			`file :: AppPath File`
			`file = opts ^. asmRunInputFile`