Almost done with cargo_klee_examples/examples/get_sign.rs

cargo_klee_examples/examples/get_sign.rs

@@ -53,6 +53,7 @@ fn main() {
 // Now locate the generated tests. Give the relative path to `klee-last`.
 //
 // [your answer here]
+// klee_tutorial/cargo_klee_examples/target/debug/examples/klee-last/
 //
 // B) Replay test cases
 //
@@ -67,6 +68,7 @@ fn main() {
 // What path of the program does this path trigger?
 //
 // [your answer here]
+// x < 0, return -1
 //
 // Just out of curiosity, you may test the other test cases as well...
 //
@@ -77,10 +79,12 @@ fn main() {
 // How does `klee-sys` and `cargo-klee` score on a 0..5 scale?
 //
 // [your answer here]
+// TODO: 5?
 //
 // If below 5, what could be done to improve the UX/IX?
 //
 // [your answer here]
+// TODO
 //
 // C) Inner workings.
 //
@@ -92,6 +96,7 @@ fn main() {
 // What modules in `klee-sys` does this feature enable?
 //
 // [your answer here]
+// TODO
 //
 // Have a look at the source code of `cargo klee`.
 // (The actual sub-command is in the folder `cargo-klee`.)
@@ -100,6 +105,7 @@ fn main() {
 // Which one will it pick, and why?
 //
 // [your answer here]
+// TODO
 //
 // Actually this is one of the "bad seeds" in the internal design.
 // Seems there is no "stable" way of controlling/retrieving the "metadata"