squiggle/packages/squiggle-lang
Quinn Dougherty b253aadc52 fixed webpack
2022-04-07 21:57:23 -04:00
..
__tests__ one last CR comment 2022-04-07 20:13:08 -04:00
src fixed webpack 2022-04-07 21:57:23 -04:00
.gitignore coverage 2022-04-06 15:19:27 -04:00
.npmignore Move to webpack 2022-03-22 10:40:14 +11:00
bsconfig.json backed out of rescript-fast-check 2022-04-07 08:55:52 -04:00
jest.config.js CR comments from #192 2022-04-07 18:38:49 -04:00
package.json backed out of rescript-fast-check 2022-04-07 08:55:52 -04:00
README.md property test framework installed but not used; describe(means) section of unit tests filled out 2022-04-06 18:57:51 -04:00
tsconfig.json Reference lang source code directly from components 2022-03-25 10:27:17 +11:00
webpack.config.js Move to webpack 2022-03-22 10:40:14 +11:00

Squiggle language

Build for development

We assume that you ran yarn at the monorepo level.

yarn build

yarn bundle is needed for a deployment.

Other:

yarn start  # listens to files and recompiles at every mutation
yarn test
yarn test:watch  # keeps an active session and runs all tests at every mutation

# where o := open in osx and o := xdg-open in linux,  
yarn coverage; o _coverage/index.html  # produces coverage report and opens it in browser

TODO: clean up this README.md

Squiggle Language

Squiggle is a language for representing probability distributions, as well as functions that return probability distributions. Its original intended use is for improving epistemics around EA decisions.

This package, @quri/squiggle-lang, contains the core language of squiggle. The main feature revolves around evaluating squiggle expressions. Currently the package only exports a single function, named "run", which from a squiggle string returns an object representing the result of the evaluation.

If using this package for tests or as a dependency, typescript typings are available and recommended to be used.

Building this package

This package doesn't have any dependencies on any other packages within the monorepo, so if you wish you can generally ignore lerna or yarn workspaces when dealing with this package in particular.

First, as per any node package, you will need to install dependencies, we recommend using yarn.

yarn

This package is mainly written in ReScript. But has a typescript interface.

ReScript has an interesting philosophy of not providing much in the way of effective build tools. Every ReScript file is compiled into .bs.js and .gen.ts files with the same name and same location, and then you can use these files in other js files to create your program. To generate these files to build the package, you run yarn build.

yarn build

.gen.ts files are created by genType, which creates typescript typings for needed parts of the codebase so that they can be easily used in typescript. These .gen.ts files reference the .bs.js files generated by rescript.

You can also go yarn start for the purposes of watching for file changes and rebuilding every time there is one.

Finally, yarn test runs the current test suite over the language.

You may notice sometimes, that there are errors about the rationale package. If you ever get these errors, yarn build should fix this issue. These errors occur because yarn build also needs to create build files that are in node_modules. So if you replace node_modules you may need to rebuild to get those files back.

Distributing this package or using this package from other monorepo packages

If you would like to distribute this package, run yarn package to compile all the js and typescript into the dist directory. This dist directory code is what's referenced by other packages in the monorepo.

Using this package

The return type of this packages only experted function run is currently quite complicated, as it has to return either a number, or a distribution, or even a representation of a function of distributions. Currently the export is simply the generated type that rescript creates, and can be quite confusing. We therefore highly recommend the use of typescript when creating tests or using this package.

Potential Issues

If you experiment with generating different types of .gen.ts files and similar, note that they won't be caught by git (because they are in .gitignore). Make sure you delete these extra files, once they are unecessary.

    rm src/rescript/**/*.gen.ts