-
# Summary
Problem: we don't have any conventions or standards on writing TLA+ code. A quick web search does not reveal any existing resource either.
We should try to define a minimal set of conv…
-
## Description
I found a case where operators defined using `LOCAL` seem to break variable substitution when using `VariantGetUnsafe`. Presumably this is due to some sort of error in th…
-
I've been working with a simplified TLA+ model to verify the behavior of SharedMutex. During this process, I encountered an unexpected issue.
## TLA+ Model and Configuration
```tla
------------…
-
Translation of temporal properties is broken, if the property contains nested temporal subformulas and quantifiers.
Take the temporal property of the MWE below;
```tla
TemporalProp == [](\A i \…
-
s-kademlia proposes requiring that the hash of a node's public key should have a certain number of trailing (or leading) zeros. This is intended to make it difficult for nodes to generate many `NodeId…
-
As suggested in https://github.com/tlaplus/CommunityModules/issues/37#issuecomment-810576974 I tried using ALIAS to make `Host` and `Clock` from the ShiViz module appear in the error trace. While ALIA…
-
## Description
Given the following spec, TLC reports the error "The subscript of the next-state relation specified by the specification
does not seem to contain the state variable \" with no f…
-
I wanted to parse TLC coverage information to render a coverage report, but I realized that I didn't understand some parts of the TLC output.
I see that coverage statistics doesn't mention some par…
-
I'm adding basic TLC models to a bunch of specs for #107 and ran into trouble with this spec, could you help? Tagging authors @konnov @josef-widder @banhday
I'm attempting to use this model:
```
…
-
## Description
Not sure if it is a bug or a feature request. Anyway, consider: CHOOSE t \in {FALSE} : FALSE
Is it possible to report an error in such a case (like TLC does)? Right now it jus…