Skip to content

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
  • 3 commits
  • 3 files changed
  • 0 commit comments
  • 2 contributors
View
2 clojure-tapl/tapl/project.clj
@@ -2,6 +2,6 @@
:description "TAPL in core.logic"
:url "https://github.com/namin/TAPL-in-miniKanren-cKanren-core.logic"
:dependencies [[org.clojure/clojure "1.4.0"]
- [org.clojure/core.logic "0.8.0-beta6-SNAPSHOT"]
+ [org.clojure/core.logic "0.8.0-rc2"]
[org.clojure/core.match "0.2.0-alpha11"]]
:dev-dependencies [[lein-swank "1.4.3"]])
View
2 clojure-tapl/tapl/src/tapl/stlce.clj
@@ -87,8 +87,6 @@
(conso [y tyy] gammap gamma)
(conde
[(== y x) (== tyb `(~'type ~tyy))]
- ;; TODO(namin): we get spurious results if we use nom/hash instead of !=.
- ;; This indicates a potential problem with nom/hash and variable noms.
[(!= y x) (lookupo gammap x tyb)]))]))
(defn typingo [gamma t tyb]
View
3 clojure-tapl/tapl/test/tapl/test/stlce.clj
@@ -19,8 +19,7 @@
(nom/fresh [x]
(typingo () `(~'fn ~(nom/tie x [x x])) q)))
'(((error (not-arrow-type _0)) :- (!= (_0 [:=> _1 _2])))
- ;; TODO(namin): The != below is spurious b/c of occurs-check. Is it worth fixing?
- ((error (incompatible-types _0 [:=> _0 _1])) :- (!= (_0 [:=> _0 _1])))))))
+ (error (incompatible-types _0 [:=> _0 _1]))))))
(deftest test-typingo-unbound-var
(is (= (run* [q]

No commit comments for this range

Something went wrong with that request. Please try again.