1. if paper has software isolation using Rust, sort into software isolation categories
2. if the paper does not, scan for incorrect claims and then sort into either irrelevant or wrong mutability (keywords: mutable, borrow, reference, invariant)

1. IM/PUI does not cause an issue because of narrow extension interface (NetBricks)
2. IM/PUI does cause an issue, and is handled
3. IM/PUI does cause an issue, and is deferred to future work
4. IM/PUI does cause an issue, and is ignored (RedLeaf, Splinter)
5. No User Language Extension/No Isolation Needs

• How many papers use Rust, how many use Rust for language extensions? (a count on these would be nice if possible)

Setting the Stage

“What does the systems research landscape change when you start writing things in Rust? What are the most important open research challenges for software written in Rust?”

• GC is now a thing if you write go
• Lots of debugging tools were shaped by pointers, etc.

Lectures

• SU-CS340R APR02024

(Ruth et al., n.d.)

One-Liner

Governments’ security guidance lack overall consensus in both formatting as well as actual practice; we find this out using treeeeees.

Novelty

• new tree similarity mechanism similar to edit distance
• first hand-labeled ontological dataset for security guidance

Notable Methods

1. download security guidance
2. label guidance into multi-level controls
3. tree distance metric for similarity

an operations research linear solution system

see simplex algorithm

DOI: 10.3389/fcomp.2021.624594

(Sadeghian, Schaffer, and Zahorian 2021)

One-Liner

Using a genetic algorithm, picked features to optimize fore; achieved \(94\%\) with just MMSE data alone (ok like duh me too). Developed ASR tool to aid.

Novelty

• Developed an ASR methodology for speech, complete with punctuations
• Used a genetic algorithm to do feature selection; NNs performed worse because “space is smaller???”

Notable Methods

Used a GRU to insert punctuations

The paper leveraged the nuke that is a bidirectional GRU, ATTENTION,