-
Notifications
You must be signed in to change notification settings - Fork 31
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
This is awesome #67
Comments
Not sure how easy this is in VSCode, but one of the things I've configured in my vim extension is coloring in all primed operators. So if you have
It would also color the |
Thank you so much for the feedback, I really appreciate it! |
@hwayne , implemented in v0.7.0 along with many other syntax highlighting improvements. BTW, any thoughts on proper indentation of TLA+/PlusCal code? |
I don't think there's enough users to have "proper" indentation, but my preference is two spaces. This is because I tend to use a lot of levels. Taking the sample someone provided in favor of four: ReplaceNode(table, id, new) ==
LET bs == table.buckets
k == CHOOSE k \in 0..Len(bs): id \in {n.id : n \in bs[k]}
old == CHOOSE old \in bs[k]: old.id = id
IN
[table EXCEPT !.buckets[k] = (bs[k] \ {old}) \cup {new}] I might rewrite it as ReplaceNode(table, id, new) ==
LET
bs == table.buckets
k ==
CHOOSE k \in 0..Len(bs):
id \in {n.id : n \in bs[k]}
old ==
CHOOSE old \in bs[k]:
old.id = id
IN
[table EXCEPT
!.buckets[k] = (bs[k] \ {old}) \cup {new}
] That's an extreme example, but it helps when working with |
No real issue, just wanted to say how much I appreciate you making this :D
The text was updated successfully, but these errors were encountered: