Howdy, gurus! I hope this is the appropriate forum for my question (please redirect if not).
Since discovering logic programming by way of William Byrd and Daniel Friedman's compelling lecture at Clojure Conj 2012 <https://youtu.be/B5EywZGFlvI>, I've been fascinated by all the potential applications (especially after the beta fuzzer produced quines and twines!). That said, I'm interested in coding a "troubleshooter" to help with my day job in tech support, and was wondering if there are similar projects I could study for inspiration. It would, for example, accept as input a number of observed symptoms, and output the most likely known issues matching all those symptoms. Similarly, it could help with upgrade path validation — e.g., by warning of known issues with existing hardware and targeted software versions. This probably sounds trivial compared with something like generating quines, but I'm having trouble wrapping my mind around how to express things like "search for known issues associated with this version and add them to a list of risks to beware" in logic programming. Is it worthwhile, even just as a brainstorming exercise, to write such a program imperatively, then "translate" it to the logic engine paradigm? I haven't finished the Reasoned Schemer, but have it on-hand if I ought to refer to a certain chapter. Thank you in advance for any guidance you might afford! -- Reuben Garrett -- You received this message because you are subscribed to the Google Groups "minikanren" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/minikanren. For more options, visit https://groups.google.com/d/optout.
