-
Updated
Dec 16, 2020 - Kotlin
verification
Here are 755 public repositories matching this topic...
-
Updated
Oct 21, 2020
-
Updated
Aug 6, 2020 - C++
-
Updated
Dec 22, 2020 - Go
-
Updated
Dec 22, 2020 - Java
-
Updated
Dec 22, 2020 - F*
-
Updated
Jun 15, 2018 - Go
-
Updated
Oct 5, 2020 - Java
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.
-
Updated
Dec 13, 2020 - Go
TravisCI (org) is dropping support for OSS builds at the end of this month, meaning they must be transferred to travis-ci.com, which uses a credit system. Builds may fail (and already are) if the number of credits is exhausted within the month.
We are recommending switching to GH Actions, but the choice of CI provider is up to the project maintainer.
See also:
-
Updated
Sep 5, 2018 - JavaScript
-
Updated
Nov 19, 2020 - C++
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.
-
Updated
Nov 25, 2020 - Rust
-
Updated
Mar 3, 2019 - Lean
-
Updated
Nov 29, 2020 - VHDL
-
Updated
Dec 12, 2020 - Go
-
Updated
Dec 11, 2016 - Objective-C
-
Updated
Dec 22, 2020 - Python
-
Updated
Dec 8, 2020 - C++
-
Updated
Dec 22, 2020 - C
-
Updated
Dec 10, 2020 - OCaml
-
Updated
Dec 13, 2020 - JavaScript
-
Updated
Dec 18, 2020
-
Updated
Feb 2, 2020 - Go
Improve this page
Add a description, image, and links to the verification topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the verification topic, visit your repo's landing page and select "manage topics."
This is very low prio, but it usually happens that when touching
Primsor 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