We don’t need a very rich parser for transcripts, but we _do_ need to reliably identify fenced code blocks, and that implies a number of subtle cases. Using a polished CommonMark parser/printer handles those subtleties for us. I chose `cmark` for a few reasons: - it’s a wrapper around `libcmark`, which is the reference implementation of CommonMark, so it should be correct; - it provides both a parser and a printer (unlike MMark); and - it is extremely fast (about 20x faster than MMark), so the fact that our home-rolled parser got to skip over everything that’s not a block isn’t an issue.). This only _partially_ uses the `cmark` printer. I think it should use it entirely, but for the cases where we do streaming output (processing UCM commands, etc.) it’s a more involved change. So I think it should be handled separately. |
||
---|---|---|
.github | ||
codebase2 | ||
contrib | ||
deps | ||
docs | ||
editor-support | ||
lib | ||
nix | ||
parser-typechecker | ||
scheme-libs/racket | ||
scripts | ||
unison-cli | ||
unison-cli-integration | ||
unison-cli-main | ||
unison-core | ||
unison-hashing-v2 | ||
unison-merge | ||
unison-share-api | ||
unison-share-projects-api | ||
unison-src | ||
unison-syntax | ||
yaks/easytest | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.mergify.yml | ||
config | ||
CONTRIBUTORS.markdown | ||
CREDITS.md | ||
dev-ui-install.sh | ||
development.markdown | ||
Dockerfile | ||
flake.lock | ||
flake.nix | ||
hie.yaml | ||
LICENSE | ||
README.md | ||
stack.yaml | ||
stack.yaml.lock | ||
weeder.dhall |
The Unison language
Overview
Unison is a modern, statically-typed purely functional language with the ability to describe entire distributed systems using a single program. Here's an example of a distributed map-reduce implementation:
-- comments start with `--`
mapReduce loc fn ifEmpty reduce data = match split data with
Empty -> ifEmpty
One a -> fn a
Two left right ->
fl = forkAt loc '(mapReduce loc fn ifEmpty reduce !left)
fr = forkAt loc '(mapReduce loc fn ifEmpty reduce !right)
reduce (await fl) (await fr)
This function can be either simulated locally (possibly with faults injected for testing purposes), or run atop a distributed pool of compute. See this article for more in-depth coverage of how to build distributed computing libraries like this.
Other resources:
- Learn about the big idea behind Unison
- Check out the project website
- Say hello or lurk in the Discord chat
- Explore the Unison ecosystem
- Learn Unison
Building using Stack
If these instructions don't work for you or are incomplete, please file an issue.
The build uses Stack. If you don't already have it installed, follow the install instructions for your platform. (Hint: brew update && brew install stack
)
$ git clone https://github.com/unisonweb/unison.git
$ cd unison
$ stack --version # we'll want to know this version if you run into trouble
$ stack build --fast --test && stack exec unison
To run the Unison Local UI while building from source, you can use the /dev-ui-install.sh
script. It will download the latest release of unison-local-ui and put it in the expected location for the unison executable created by stack build
. When you start unison, you'll see a url where Unison Local UI is running.
See development.markdown
for a list of build commands you'll likely use during development.
Language Server Protocol (LSP)
View Language Server setup instructions here.
Codebase Server
When ucm
starts it starts a Codebase web server that is used by the
Unison Local UI. It selects a random
port and a unique token that must be used when starting the UI to correctly
connect to the server.
The port, host and token can all be configured by providing environment
variables when starting ucm
: UCM_PORT
, UCM_HOST
, and UCM_TOKEN
.
Configuration
See the documentation for configuration here