This is very low prio, but it usually happens that when touching Prims or some other file high in the dependency graph, we get spurious diffs in many other files. Since we check-in the snapshot, and we need to have it up-to-date, we get very verbose commits when nothing relevant changed. Plus, when something did change, it's hard to spot.

Example: I removed a few lines in prims and get things

Cocotb deposits values on signals. It does not behave like another driver. This should be made more explicit. And this is where the documentation for Force, Release, and Freeze should go, not in the middle of the quickstart.

To accompany this an example of interacting with a tri-state bus would be very useful, since that is the most likely reason those behaviors would be used.

eg. SomeProvider or some-provider

VUnit.add_source_files_from_csv() only passes vhdl_standard kwarg to Library.add_source_file(). However, my file gatherer uses .ahd file extensions to denote altera, .xhd to denote xilinx, and so on. I need the file_type available at least so I can tell VUnit that those file types are still vhdl, but all arguments should be available.