ChapelCon/ChapelCon2025-Slides
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix numerous typos

Browse Source 
Signed-off-by: Danila Fedorin <daniel.fedorin@hpe.com>
This commit is contained in:
Danila Fedorin
2025-10-02 17:55:57 -07:00
parent 985763d19c
commit 9c24aac627
2 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
alloy/slides.md
View File

@@ -50,7 +50,7 @@ I have a story in three parts.
- I had little background in Alloy, but some background in (formal) logic
3. This led me to discover a bug in the compiler that I then fixed.
- Re-creating the bug required some gymanstics that were unlikely to occur in practice.
- Re-creating the bug required some gymnastics that were unlikely to occur in practice.
---
@@ -160,7 +160,7 @@ Here, we search the scope of `R` and `M1`, but **only for public symbols**.
We want to:
- Respect the priority order
- Including prefering methods over non-methods
- Including preferring methods over non-methods
- As a result, we search the scopes multiple times
- Avoid any extra work
- This includes redundant re-searches
@@ -208,7 +208,7 @@ Code notes `previousFilter` is an approximation.
* `previousFilter` is an approximation.
* For `previousFilter = PUBLIC` and `filter = METHOD_FIELD`, we get
`previousFilter = 0`, indicating no more searches should be donne.
`previousFilter = 0`, indicating no more searches should be done.
* But we're missing private non-methods!
* However, no case we knew of hit this combination of searches, or any like it.
* All of our language tests passed.
@@ -326,7 +326,7 @@ eventually theSunIsInTheSky
# Search Configuration in Alloy
Instead of duplcating `METHOD` and `NOT_METHOD`, use two sets of flags (the regular and the "not").
Instead of duplicating `METHOD` and `NOT_METHOD`, use two sets of flags (the regular and the "not").
```alloy
enum Flag {Method, MethodOrField, Public}
@@ -450,7 +450,7 @@ To combine several statements, we make it so that the "next" state of one statem
</div>
</div>
This is reminiscent of sequencing hoare triples:
This is reminiscent of sequencing Hoare triples:
$$
\{ P \} \; s_1 \; \{ Q \} \; s_2 \; \{ R \}
@@ -634,13 +634,13 @@ wontFindNeeded: run {
![bg left width:600px](./bug.png)
We need some gymnastics to figure out what varibles make this model possible.
We need some gymnastics to figure out what variables make this model possible.
Alloy has a nice visualizer, but it has a lot of information.
In the interest of time, I found:
* If the compiler searches a scope firt for `PUBLIC` symbols, ...
* If the compiler searches a scope first for `PUBLIC` symbols, ...
* ...then for `METHOD_OR_FIELD`, ...
* ...then for any symbols, they will miss things!