Tahina Ramananandro (professional account)

The Docker Windows image (ewerest) is now based on VS2017 and successfully builds, so all of these should work now.

Issue #4 already tracks most of those. Specifically for switching to Python 3.5, I opened issue #54

Boxes checked above track progress on QuackyDucky branch `taramana_lowparse`. - [x] Merge into QuackyDucky `master` - [x] Test with miTLS

Thank you Alan for submitting this issue. Right now EverParse uses the .3d filename as is to generate the corresponding F* module name. Thus, as of now .3d filenames must...

The Docker Windows image (ewerest) already has most, if not all, of these steps automated (now for VS2017 actually.) It now remains to move them back to `everest check`

Yes, you need QD_HOME set to the directory where EverParse is installed. By the way, this README.md seems really outdated, it does not mention such dependencies as EverParse, HACL*, or...

When doing `./everest check`, into which configuration file was the call to `.opam/.../init.sh` appended? Do you have more than one of `.bash_profile`, `.profile`, etc.?

I should not break calling `3d --batch` on .3d files that **do not** depend on each other but live in different directories. If I am not careful, then I might...

Thank you for reporting. f6dc2f1bf910d6f206c489197296c2700db442d2 is doing exactly that, and I'll be merging it soon if CI allows it. However, ideally, we should rather fix `FStar_Extraction_ML_PrintML.ml` if possible. So, I...

Just merged. (As an aside, someone also set such an upper bound for the latest published opam package: ocaml/opam-repository#21990 Let me now repurpose this issue to ask for help fixing...