verification

They are all currently written in groovy; I'd like to migrate them to the build.gradle.kts format to make the whole project Kotlin-based.

I think this can be done in steps, migrating one build.gradle file at a time - not sure about it though.

Other than BEFORE TX we could expose AFTER TX as a SQL method

A formula like forall x1. forall. x2. exists x3. phi gets resugared to, and hence pretty printed as, forall x1 x2 x3. phi. The bug is in the uncurry function in FStar.Syntax.Reguar.fs.

Several users have asked for an example of how to use the makefiles in projects that contain precompiled and/or encrypted IP cores or libraries. There should be a simple example. It will likely not work for them, but could act as a template.

Alternatively, documentation or an explicit API for these objects would also help.

Here is the problem:

$ make compile
Traceback (most recent call last):
File "C:\My_Designs\probe_fpga_design_1\run.py", line 336, in
main()
File "C:\My_Designs\probe_fpga_design_1\run.py", line 181, in main
vu.add_osvvm()
File "c:\my_designs\probe_fpga_design_1\deps\vunit\vunit\ui_init_.py", line 1030, in add_osvvm
self.builtins.add("osvvm")
File "c:\my

Prusti uses collections such as HashSet and HashMap, which use a high quality hasher that provides high protection against collisions. However, that hasher is relatively slow and we don't care about HashDoS attacks. So, replacing those collections with FxHashSet and FxHashMap should always be better.

Collections: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_data_structures/fx/i