diff options
author | Yann Herklotz <git@yannherklotz.com> | 2023-05-11 19:38:03 +0100 |
---|---|---|
committer | Yann Herklotz <git@yannherklotz.com> | 2023-05-11 19:38:03 +0100 |
commit | 47c1289ff658a5aec71635d79ffe30bb29a07876 (patch) | |
tree | 56cf6b959e37fed88c492d34defd3d7ec40e7148 /content/zettel/2e1c3a.md | |
parent | fbe0fc62120348f582dc4db2b614078943d0764b (diff) | |
download | zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.tar.gz zk-web-47c1289ff658a5aec71635d79ffe30bb29a07876.zip |
Add content
Diffstat (limited to 'content/zettel/2e1c3a.md')
-rw-r--r-- | content/zettel/2e1c3a.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/content/zettel/2e1c3a.md b/content/zettel/2e1c3a.md new file mode 100644 index 0000000..027d1c4 --- /dev/null +++ b/content/zettel/2e1c3a.md @@ -0,0 +1,21 @@ ++++ +title = "Abstract the nested if-statements into a list" +author = "Yann Herklotz" +tags = [] +categories = [] +backlinks = ["2e1c3"] +forwardlinks = ["2e1c5", "2e1c3b"] +zettelid = "2e1c3a" ++++ + +The main problem with the nested if-statements is that they are ordered, +meaning that one can not simply order them and end up with the same +behaviour. This depends on the fact of if two predicates are satisfiable +or not, which affects on if they can be switched or not. + +This can be solved with a similar solution to the full SAT solution +([\#2e1c5]), whereby the if-statements are collapsed into a list of +conditionals, out of which only one can be active at a time. This means +that their order does not matter, and that they can then be sorted. + + [\#2e1c5]: /zettel/2e1c5 |