-
On macOS 10.14.6 with the recent version of AdobeReader DC 2019.012.20036 and Toolbox 1.6.0 producing a spec's pretty-printed PDF causes the Toolbox to crash with a sigserv. The built-in Preview app …
lemmy updated
4 years ago
-
TLC reports 0 coverage for the indicated conjunct of the next-state action below:
```tla
VARIABLE x
Spec == /\ x = 0
/\ [][/\ x' = (x+1)%5
/\ x' = (x+1)%5 \*
lemmy updated
5 years ago
-
I fixed this myself by renaming some files, I don't yet have the woo to make a pull request. I have absolutely no idea what I am doing BTW, I was just trying out an example to test I had installed t…
-
This issue documents my proposal to extend the PlusCal language with features that enable composability.
Currently one PlusCal algorithm cannot interact with another in any way. They cannot refer t…
-
In other words, the same label name could be reused across processes/procedures (and the PlusCal to TLA+ translator is responsible for making sure labels are unique).
Make sure the atomicity infere…
-
Consider the following pluscal spec:
```
-------------------------------- MODULE bug --------------------------------
(* --algorithm bug
variables foo = 0 \* missing separator token
fair pr…
-
The PlusCal user manual says in section 2.1 that \neq can be used as well as # or \=. However this doesn't seem to work, and it doesn't appear in the table of translations.
(Sorry if this isn't the…
hcs64 updated
6 years ago
-
The `either` statement executes a random non-blocking clause. We could implement this with `select` in Go, but it's difficult to get it into a format where `select` works.
Original issue: https://b…
-
We want to be able to compile a variety of single threaded PlusCal algorithms before moving on to dealing with concurrency. This should involve handling set construction, complicated variable init…
-
On https://www.learntla.com/pluscal/behaviors/
Does not follow label rules from http…