-
I tried this code:
```rust
#[kani::proof]
fn test_rem() {
let dividend: f32 = kani::any::().into();
let divisor: f32 = kani::any::().into();
kani::assume(divisor != 0.0);
let …
-
Rework the spawn procedure a bit:
- In case of a client we should request the host to spawn a summon for us.
- In case of a host we should listen for these requests and make the decision on whethe…
-
Need to determine what the procedures are for approving the implementation of WIS2 Global Services and WIS2 nodes to ensure that they are compliant to the WIS2 regulations.
Notes, this is separate fro…
-
I don't know that this is an actionable ticket just yet but I also wanted to make sure we don't lose this context.
We have right now a list of hard-coded metrics that we manually update quite regul…
-
We've observed many developers execute the strategy without stepping through the tool. Once they get ahead of where the tool is, there's no easy way for them to synchronize their state with the tools …
-
### Dafny version
4.0.0
### Code to produce this issue
Unfortunately, I don't have an example input handy at the moment. I'll edit this issue to add one when I do.
### Command to run and r…
atomb updated
2 months ago
-
There is inconsistency with the use of "Partners" versus "ESIPs" throughout the P&P. For clarity, this should be reviewed and updated.
-
Steps to reproduce:
1. `cargo new foo`
2. `cd foo`
3. `cargo add aws-lc-sys`
4. Put the following in `src/main.rs`:
```rust
use aws_lc_sys::RAND_bytes;
#[kani::proof]
fn foo() {
let mut…
-
See the [proposal template](https://github.com/brightway-lca/enhancement-proposals/blob/main/proposals/0001-bep-template.md).
-
There are two tickets relating to presentation of the viability-related data for this gene, Tmem63b.
This first ticket focuses on what could be potentially confusing for users. The other ticket is #7…