672e400a2a
Core transformations apply to the whole InfoTable, the REPL needs to apply Core transformations to the single node that it compiles from the user input string. The solution in this commit is to: 1. Compile the input string as before to obtain a Core Node. 2. Add this Node to a copy of the Core InfoTable for the loaded file. 3. Apply the (CLI specified) Core transformations to this InfoTable. 4. Extract the (now transformed) Node from the InfoTable. We can think of a way to improve this, maybe when we tackle allowing the user to make new definitions in the REPL. As soon as compilation of pattern matching is complete we should enable some (all?) Core transformations by default. Example: At the moment we get the following result in the REPL: ``` juvix repl ... Stdlib.Prelude> 1 + 1 suc (suc zero) ``` After this commit we can turn on `nat-to-int` transformation: ``` juvix repl -t nat-to-int Stdlib.Prelude> 1 + 1 2 ``` * Part of https://github.com/anoma/juvix/issues/1531 |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| app | ||
| assets | ||
| bench | ||
| c-runtime | ||
| docker | ||
| docs/org | ||
| examples | ||
| gnuplot | ||
| juvix-stdlib@0ad2c5e207 | ||
| licenses | ||
| runtime | ||
| src/Juvix | ||
| test | ||
| tests | ||
| .clang-format | ||
| .github_changelog_generator | ||
| .gitignore | ||
| .gitmodules | ||
| .hlint.yaml | ||
| .pre-commit-config.yaml | ||
| .pre-commit-hooks.yaml | ||
| book.toml | ||
| cabal.hie.yaml | ||
| cabal.project | ||
| changelog.org | ||
| cntlines.sh | ||
| LICENSE | ||
| Makefile | ||
| package.yaml | ||
| README.org | ||
| stack.hie.yaml | ||
| stack.yaml | ||
Juvix
<a href="https://github.com/anoma/juvix/actions/workflows/ci.yml">
<img alt="CI status" src="
" />
</a>
<a href="https://github.com/anoma/juvix/actions/workflows/pages/pages-build-deployment"><img
src="
"
alt="pages-build-deployment" /></a>
<a href="https://github.com/anoma/juvix/tags"> <img alt="" src="https://img.shields.io/github/v/release/anoma/juvix?include_prereleases" /> </a>
<a href="https://github.com/anoma/juvix/blob/main/LICENSE">
<img alt="LICENSE" src="
" />
</a>
<a href="https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=455254004">
<img height="20pt" alt="Open the Juvix Standard Lib in Github Codespace" src="
" />
</a>
<a href="https://github.com/anoma/juvix"> <img align="right" width="300" height="300" alt="Juvix Mascot" src="assets/images/tara-seating.svg" /> </a>
Description
Juvix is a research programming language created by Heliax as a first step toward creating more robust and reliable alternatives for formally verified smart contracts than existing languages. The Juvix language is constantly evolving, open-source, functional, and statically typed with special support for compiling validity predicates to WebAssembly, which can be deployed to various distributed ledgers including Anoma.
The Juvix language and related tools are documented in the Juvix book. To write
and test Juvix programs, you can use your favorite text editor, the juvix
command line tool, the Juvix Github Codespace, and the Juvix Standard Lib Codespace. However, we recommend using the juvix-mode in Emacs or the
plugin in VSCode.
Quick start
See Quick start to start with Juvix.
The Juvix programming language
Juvix provides a high degree of assurance. The Juvix compiler runs several static analyses which guarantee the absence of runtime errors. Analyses performed include termination, arity, and type checking. As a result, functional programs, especially validity predicates, can be written with greater confidence in their correctness.
Some of the language features in Juvix include:
- unicode syntax
- parametric polymorphism
- inductive and parametric data types
- higher-order functions
- implicit arguments
- holes in expressions
- axioms for non-computable terms
The Juvix module system further permits splitting programs into several modules to build libraries which can be later documented by generating HTML files based on the codebase, see for example, the Juvix standard library's website. For further details, please refer to the Juvix book which includes our latest updates.
Community
Join us on our Discord server
This project is part of a bigger effort called Anoma. Anoma is a suite of protocols and mechanisms for self-contained, self-sovereign coordination. Join the Anoma project.