-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A set of suggestions and confusing bits #37
Comments
Thanks for these suggestions! I plan to look at them all this week. |
Ugh finally looking at it late
|
This one can be ticked off now:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a set of all the suggestions I had or confusing things I noticed during a read-through. I hope you don't mind the list of unrelated items here, but I didn't want to spam the issues board. I know this is very much a work in progress so some issues aren't unexpected -- thanks for making this resource, and take or leave these suggestions as you wish.
pc
probably stands for program counter.A => B
is equivalent to~A \/ B
was the most helpful piece to help me understand=>
. Many programmers are already have an intuition for this form. It could be just me, but explaining it like "~A \/ B
is really helpful, so TLA+ gives us syntactic sugar in the form of=>
" would make for a more natural explanation. Just something to consider.Tip
in the Structured Data chapter ("State sweeping is when...", then "... trick known as state sweeping").<>
is used in an example spec before it is defined.WF_v
andSF_v
, but the English explanation usesWF_x
andWF_vars
. This is kind of confusing. Does it matter?<=>
is used in "General Tips" and/=
in the Goroutines example without either being defined. (The/=
looks like it could be#
?)The text was updated successfully, but these errors were encountered: