This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-18
Channels
- # admin-announcements (10)
- # boot (260)
- # cider (44)
- # clojure (226)
- # clojure-berlin (24)
- # clojure-dev (68)
- # clojure-germany (5)
- # clojure-india (14)
- # clojure-italy (3)
- # clojure-japan (21)
- # clojure-poland (34)
- # clojure-russia (20)
- # clojure-spain (2)
- # clojure-uk (8)
- # clojurescript (86)
- # core-async (38)
- # core-typed (70)
- # datomic (41)
- # docs (8)
- # editors (7)
- # euroclojure (6)
- # instaparse (2)
- # jobs (8)
- # ldnclj (47)
- # om (17)
- # other-lisps (1)
- # reactive (1)
- # reading-clojure (8)
- # reagent (13)
- # sneer (1)
- # sneer-br (1)
ambrosebs: well, technically, cursive gave me a hint, my eyes just got not used to recognize that pattern in this case (unused function version used function). in cursive a function becomes a used function too, when it gets a type annotation. Apart from that, this was the first time it happens, so I think there is no need for this to be caught by core.typed It's more a nice to have from my point of view
core.typed looks up the current impl, say, clojurescript and tries to load “foo/bar.cljs"
now it’d be easy to just see if the resource exists and if not try cljc in both cases (clojure and cljs)
but what happens if there are two files, one with clj and one with cljc? is that even a thing?
[[clojure.core$ex_info invoke "core.clj" 4593] [clojure.core.typed.errors$int_error invoke "errors.clj" 39] [clojure.core.typed.errors$int_error invoke "errors.clj" 36] [clojure.core.typed.analyze_clj$ast_for_file invoke "analyze_clj.clj" 251] [clojure.core.typed.analyze_clj$ast_for_ns invoke "analyze_clj.clj" 288] [clojure.core.typed.collect_utils$collect_ns_STAR_ invoke "collect_utils.clj" 79] [clojure.core.typed.collect_phase$collect_ns invoke "collect_phase.clj" 64] [clojure.core.typed.check_ns_common$check_ns_info$fn__45278$fn__45279 invoke "check_ns_common.clj" 66] [clojure.core.typed.check_ns_common$check_ns_info$fn__45278 invoke "check_ns_common.clj" 58]
cool! you need to have your name on http://clojure.org/contributors first
@ambrosebs: how’s the crowfunding campaign going? 😄
I’m wondering — in CONTRIBUTING.md it says that everything goes through JIRA etc but I see 4 Pull Requests in the github repo — where should I submit mine?
post on gradual typing for clojure http://frenchy64.github.io/2015/06/19/gradual-typing.html
@ambrosebs: great post, I found it illuminating
indeed, very nice
@ambrosebs: awesome post!
@ambrosebs: in a nutshell, could I say that Optional Types care about "type check or not" within a language, whereas Gradual Typing is more related with the boundaries between type systems?
following your article I could imagine some gradual type system between C and FFI as an example
indeed, but it got me to see the article so thanks @ambrosebs
@ambrosebs: interesting article, well written, thank you