2013-12-30 14:32:36 +01:00
|
|
|
;; Copyright (c) 2014 Morten Linderud <mcfoxax@gmail.com>
|
|
|
|
|
|
|
|
|
|
;; Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
|
;; copy of this software and associated documentation files (the "Software"),
|
|
|
|
|
;; to deal in the Software without restriction, including without limitation
|
|
|
|
|
;; the rights to use, copy, modify, merge, publish, distribute, sublicense,
|
|
|
|
|
;; and/or sell copies of the Software, and to permit persons to whom the
|
|
|
|
|
;; Software is furnished to do so, subject to the following conditions:
|
|
|
|
|
|
|
|
|
|
;; The above copyright notice and this permission notice shall be included in
|
|
|
|
|
;; all copies or substantial portions of the Software.
|
|
|
|
|
|
|
|
|
|
;; THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
|
;; IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
|
;; FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
|
;; THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
|
;; LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
|
|
|
|
;; FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
|
|
|
|
|
;; DEALINGS IN THE SOFTWARE.
|
|
|
|
|
|
Give `require` the same features as `import` (#1142)
Give `require` the same features as `import`
You can now do (require foo), (require [foo [a b c]]), (require [foo [*]]), and (require [foo :as bar]). The first and last forms get you macros named foo.a, foo.b, etc. or bar.a, bar.b, etc., respectively. The second form only gets the macros in the list.
Implements #1118 and perhaps partly addresses #277.
N.B. The new meaning of (require foo) will cause all existing code that uses macros to break. Simply replace these forms with (require [foo [*]]) to get your code working again.
There's a bit of a hack involved in the forms (require foo) or (require [foo :as bar]). When you call (foo.a ...) or (bar.a ...), Hy doesn't actually look inside modules. Instead, these (require ...) forms give the macros names that have periods in them, which happens to work fine with the way Hy finds and interprets macro calls.
* Make `require` syntax stricter and add tests
* Update documentation for `require`
* Documentation wording improvements
* Allow :as in `require` name lists
2016-11-03 08:35:58 +01:00
|
|
|
(require [hy.contrib.multi [defmulti]])
|
2013-12-30 14:32:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
(defn test-basic-multi []
|
|
|
|
|
"NATIVE: Test a basic defmulti"
|
|
|
|
|
(defmulti fun
|
|
|
|
|
([] "Hello!")
|
|
|
|
|
([a] a)
|
|
|
|
|
([a b] "a b")
|
|
|
|
|
([a b c] "a b c"))
|
|
|
|
|
|
|
|
|
|
(assert (= (fun) "Hello!"))
|
|
|
|
|
(assert (= (fun "a") "a"))
|
|
|
|
|
(assert (= (fun "a" "b") "a b"))
|
|
|
|
|
(assert (= (fun "a" "b" "c") "a b c")))
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(defn test-kw-args []
|
|
|
|
|
"NATIVE: Test if kwargs are handled correctly"
|
|
|
|
|
(defmulti fun
|
|
|
|
|
([a] a)
|
|
|
|
|
([&optional [a "nop"] [b "p"]] (+ a b)))
|
|
|
|
|
|
|
|
|
|
(assert (= (fun 1) 1))
|
|
|
|
|
(assert (= (apply fun [] {"a" "t"}) "t"))
|
|
|
|
|
(assert (= (apply fun ["hello "] {"b" "world"}) "hello world"))
|
|
|
|
|
(assert (= (apply fun [] {"a" "hello " "b" "world"}) "hello world")))
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(defn test-docs []
|
|
|
|
|
"NATIVE: Test if docs are properly handled"
|
|
|
|
|
(defmulti fun
|
|
|
|
|
"docs"
|
|
|
|
|
([a] (print a))
|
|
|
|
|
([a b] (print b)))
|
|
|
|
|
|
|
|
|
|
(assert (= fun.--doc-- "docs")))
|