News for hackers. Stuff that matters.
Re:The internals of testing in Rust in 2018 by judofyr on Tuesday July 24, 2018 @04:15AM (#17599041)
Well, I did look at it, but it was difficult to figure out how control-flow is structured. Is every “basic block” a single “el”, or is the CFG structured inside the binary tree? How are variables handled? Are there load expressions? Do you use something similar to phi-nodes to merge values from different branches? How do you do analysis? Do you walk over the expression tree and store the results (e.g. in constant propagation) on the nodes themselves? Do you use a separate cache/hashmap?
Re:The internals of testing in Rust in 2018 by WalterBright on Tuesday July 24, 2018 @04:38AM (#17599140)
Basic blocks form a linked list (block*), and each basic block has a tree of elem's. Control flow is done with the basic block "predecessor" and "successor" lists.