Request for review?

32 views
Skip to first unread message

Shane Miller

unread,
3:26 AM (18 hours ago) 3:26 AM
to tlaplus
Good day,

I've prepared a lengthy paper on TLA with a focus on practical issues. I'm wondering if there's subscribers here who are willing to give me feedback? Find attached: first three pages which includes table of contents. Chapters 12, 13 coming. There's undoubtedly errors that need fixing.

If you're interested we can exchange information through Github:

https://github.com/gshanemiller/tla-examples

The full paper and examples are there.

Thank you!
 
brief.pdf

Andrew Helwer

unread,
10:58 AM (11 hours ago) 10:58 AM
to tla...@googlegroups.com
Hi Shane,

Looks interesting; before reading, is this an AI-assisted effort or did you write it all yourself?

Thanks,

Andrew

--
You received this message because you are subscribed to the Google Groups "tlaplus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tlaplus+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/tlaplus/f69e71e8-e803-45f9-9211-3c1d080feb64n%40googlegroups.com.

Shane Miller

unread,
4:42 PM (5 hours ago) 4:42 PM
to tlaplus
100.0% my own work

Ambareesh Jayakumari

unread,
5:24 PM (4 hours ago) 5:24 PM
to tla...@googlegroups.com
Hi Shane,

Looks amazing, and would love to read. Few questions:

1. How would you prefer the feedback / clarifications? Would creating a GitHub suffice, or is it better done over email? 

2. What kind/level of feedback are you looking  for at this stage?  - higher level correctness or does lower level nits be useful as well? 

Best,
Ambareesh
“I’ll live the focused life, because it’s the best kind there is" (Winifred Gallagher)


Shane Miller

unread,
6:26 PM (3 hours ago) 6:26 PM
to tlaplus
Ambareesh,

Thank you for taking time and reaching out!


>How would you prefer the feedback 
Let's use Github.
1. Make new issues for errors in the pdf text
2. Make pull requests for errors in the examples

>higher level correctness or does lower level nits be useful as well?
Both are fine, and appreciated. 

- errors in the linked examples must be fixed
- errors in the language reference sections are bad, and should be fixed
- I'm pretty sure there's a few errors on executability (which drags in fairness) in the TLA reference. Because this issue is so different from C/C++ it's got to be corrected. Getting users fluent and comfortable with flow control is important

Regards
Reply all
Reply to author
Forward
0 new messages