807b3b1770
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> |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| app | ||
| assets | ||
| bench | ||
| c-runtime | ||
| docker | ||
| docs/org | ||
| examples | ||
| gnuplot | ||
| juvix-stdlib@7e54415ffa | ||
| 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.