Ian Sweet

Okay, I was able to create an `opam` package for the `sets` module. Now I am going to see if I did it correctly, and if `dune` can access this...

Currently I'm imagining things like: ``` src/ regexp.ml regexp.mli nfa.ml nfa.mli dune dep/ sets/ sets.cmo sets.cmi Makefile sets.opam bin/ viz.ml dune test/ testUtils.ml public.ml dune ``` and you'd just need...

Then anytime you have things you want to distribute as binary, you stick them in `dep ` and write a quick little `.opam` file and do a `opam pin add`...

And you can even add an OCaml version constraint for 4.04.x so that when students try to use the wrong version of OCaml, `opam` will yell at them.

I've added a first crack at my idea. It's here (second commit on the branch): https://github.com/anwarmamat/cmsc330spring18-public/pull/6/commits/1f54b08fab9147eccab6a568cfc47ac85cca355a The basic idea is to turn any dependencies whose source you don't want to...

Yeah, in order to build the `*.cmxa` you need the `*.cmx`. Seems strange that you can't run tests, since they should be able to be run via the compiled version...

We're also interested in using SynLig for parsing `assume property` and `assert property` statements in SystemVerilog. Is that currently possible? I've tried a simple example with `read_systemverilog -formal -defer`, and...