t; I might be overlooking some basic things.
>>>
>>> Hereby
>>>
>>> $lein version
>>> Leiningen 2.6.1 on Java 1.8.0_102 Java HotSpot(TM) 64-Bit Server VM
>>> $ lein deps :tree
>>> Possibly confusing dependencies found:
>>> [cide
sic things.
>
> Hereby
>
> $lein version
> Leiningen 2.6.1 on Java 1.8.0_102 Java HotSpot(TM) 64-Bit Server VM
> $ lein deps :tree
> Possibly confusing dependencies found:
> [cider/cider-nrepl "0.8.1"] -> [org.clojure/java.classpath "0.2.0"
> :exclusio
repl
> Initializing core.typed ...
> WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace:
> clojure.tools.analyzer.utils, being replaced by: #'clojure.tools.analyzer.
> utils/boolean?
> WARNING: boolean? already refers to: #'clojure.core/boolean? in name
lke van Foeken
>
>
> Op woensdag 31 augustus 2016 11:17:09 UTC+2 schreef Ambrose
> Bonnaire-Sergeant:
>
>> Hi,
>>
>> The latest core.typed release has support for generating
>> clojure.spec specs from unit tests.
>>
>> [org.clojure/core.typed &
Hi,
The latest core.typed release has support for generating
clojure.spec specs from unit tests.
[org.clojure/core.typed "0.3.25"]
...; for very recent releases
:repositories {"sonatype-oss-public"
"https://oss.sonatype.org/content/groups/public/"}
Here's
If you're at the repl, you should use `cf` to evaluate `defalias` also.
Sorry for the late response.
Thanks,
Ambrose
On Thu, Oct 29, 2015 at 9:23 PM, JvJ wrote:
> Reposting from the core.typed google group. Didn't get a response.
>
> I'm just starting with core.typed,
Reposting from the core.typed google group. Didn't get a response.
I'm just starting with core.typed, and I can't seem to get it to work
properly in the REPL.
I start by defining an alias (Fhtagn), but when I later try to type-check
it, the name "Fhtagn" is unresol
I got a working version in my fork of emacs-live (if you happen to use it).
See here
https://github.com/arichiardi/emacs-live/blob/ar-stable/packs/dev/clojure-pack/config/flycheck-clojure-conf.el
On Thursday, September 24, 2015 at 1:36:07 PM UTC-7, JvJ wrote:
>
> Hi,
>
> Maybe this topic has alre
It relies on kibit, eastwood and core.typed to provide warnings and errors.
This means support for other dialects will be available when those projects
add support.
On Saturday, September 26, 2015 at 12:19:03 AM UTC+2, JvJ wrote:
>
> Lars, thanks for telling me about squiggly-clojure. It
Lars, thanks for telling me about squiggly-clojure. It seems great.
Do you know if there's a way to get it to work with cljc and/or cljs files?
Currently, it only seems to work with clj files.
On Thursday, 24 September 2015 13:36:07 UTC-7, JvJ wrote:
>
> Hi,
>
> Maybe this topic has already be
Hello,
Have you given typed-clojure-mode a shot? If there are any issues, post on
the github page and I'll address them. There are similar modes for vim and
light table.
https://github.com/typedclojure/typed-clojure-mode
John
On Thursday, September 24, 2015 at 1:36:07 PM UTC-7, JvJ wrote:
>
Cider has a cider-run command as an easy way to run specific functions. You
can cook up some simple elisp to load the buffer and then call that
function.
On 25 Sep 2015 10:22 am, "Lars Andersen" wrote:
> Something like this doesn't exist in CIDER, so you have to write some
> elisp yourself, if yo
Something like this doesn't exist in CIDER, so you have to write some elisp
yourself, if you want it.
While not exactly what you've envisioned, I think the best solution is
this: https://github.com/clojure-emacs/squiggly-clojure
On Thursday, September 24, 2015 at 10:36:07 PM UTC+2, JvJ wrote:
Hi,
Maybe this topic has already been addressed, but if it has been, I couldn't
find it.
When using cider, I tend to user C-c C-l a lot to reload my namespaces as
I'm writing them.
Is there an easy way to incorporate type-checking into this process? A
load-file-and-typecheck command?
I've a
Hm,
Is it possible that core.typed may be influenced by the repl state? New day
and a new try I got these both working:
(t/ann dt->hiccup [(t/HVec [Keyword (t/U Keyword (t/HVec [Keyword Number]))
t/Any t/Any *]) -> html-form-group])
(defmulti dt->hiccup (t/fn [col :- (t/HVec [Key
I added your explanation the the wiki of core.typed:
https://github.com/clojure/core.typed/wiki/Intersection-vs.-Union I hope
that is fine for you.
Am Donnerstag, 16. April 2015 23:25:42 UTC+2 schrieb Ambrose
Bonnaire-Sergeant:
>
> It might help thinking in terms of Java interfaces, F
(first (second col))
>>>>>> (second col
>>>>>>
>>>>>> And here comes the error message when checking this function:
>>>>>>
>>>>>> Type Error (leiningen/td_to_hiccup.
p.clj:25:34) Polymorphic function
>>>>> first could not be applied to arguments:
>>>>> Polymorphic Variables:
>>>>> x
>>>>>
>>>>> Domains:
>>>>> (t/HSequential [x t/Any *])
>>>>>
;>>> Domains:
>>>> (t/HSequential [x t/Any *])
>>>> (t/Option (t/EmptySeqable x))
>>>> (t/NonEmptySeqable x)
>>>> (t/Option (clojure.lang.Seqable x))
>>>>
>>>> Arguments:
>>>
s:
>>>> (t/HSequential [x t/Any *])
>>>> (t/Option (t/EmptySeqable x))
>>>> (t/NonEmptySeqable x)
>>>> (t/Option (clojure.lang.Seqable x))
>>>>
>>>> Arguments:
>>>> (t/U Keyword
able x))
>>>
>>> Arguments:
>>> (t/U Keyword (t/HVec [clojure.lang.Keyword java.lang.Number]))
>>>
>>> Ranges:
>>> x :object {:path [(Nth 0)], :id 0}
>>> nil
>>> x
>>> (t/Option x)
&g
Keyword java.lang.Number]))
>>
>> Ranges:
>> x :object {:path [(Nth 0)], :id 0}
>> nil
>> x
>> (t/Option x)
>>
>> in: (first (second col))
>> in: (first (second col))
>>
>>
>> Excep
{:path [(Nth 0)], :id 0}
> nil
> x
> (t/Option x)
>
> in: (first (second col))
> in: (first (second col))
>
>
> ExceptionInfo Type Checker: Found 1 error clojure.core/ex-info (core.clj:
> 4403)
>
> My assumption is that the check (if
Info Type Checker: Found 1 error clojure.core/ex-info (core.clj:
4403)
My assumption is that the check (if (vector? (second col will return only
true if it is this type: (HVec [Keyword Number]). However, I have the
impression that core.typed does not resolve the if expression properly.
Or maybe I a
:
>
>> Hi,
>> Thanks for replying, I've signed the CA and forwarded this post to the
>> core.typed mailing list.
>> Can you tell me what should I do for now?
>> Thanks,
>> Z.Shang
>>
>> On Tuesday, March 17, 2015 at 5:49:34 PM UTC-7, Di Xu wr
Read code base, submit some patches to get familiar with the process, etc.
Also you can reach Ambrose to discuss your idea & proposal.
Di Xu
2015-03-18 13:29 GMT+08:00 ZhanLin Shang :
> Hi,
> Thanks for replying, I've signed the CA and forwarded this post to the
> core.
Hi,
Thanks for replying, I've signed the CA and forwarded this post to the
core.typed mailing list.
Can you tell me what should I do for now?
Thanks,
Z.Shang
On Tuesday, March 17, 2015 at 5:49:34 PM UTC-7, Di Xu wrote:
>
> Welcome,
>
> I participated core.typed GSoC last year,
Welcome,
I participated core.typed GSoC last year, and happy to see another Chinese
student interested in core.typed project, you may forward your email to
core.typed mail list[0], also you should first sign CA[1] (if you haven't)
before any of your patches get accepted by core.typed or any
Hello all,
My name is Zhanlin Shang and I'd like to work with the core.typed
Annotations and Macros mentored by Ambrose Bonnaire-Sergeant this summer.
This is the first time for me to take part in this kind of event and I hope
this mailing list is the right place.
I'm a s
Thanks Di Xu. Good to know. I have joined the core.typed group and will
post my questions there from now on.
J
On Friday, December 12, 2014 11:41:43 PM UTC-6, Jesse wrote:
>
> Hi guys, Does anyone know how to properly deal with refs in core.typed? I
> am running into trouble. When I
2014-12-13 13:41 GMT+08:00 Jesse :
> Hi guys, Does anyone know how to properly deal with refs in core.typed? I
> am running into trouble. When I try to do stuff like this:
>
> (ann my-ref (Ref1 (U Kw nil)))
>> (def my-ref (ref #{}))
>
>
> I get this error:
>
>&g
Hi guys, Does anyone know how to properly deal with refs in core.typed? I
am running into trouble. When I try to do stuff like this:
(ann my-ref (Ref1 (U Kw nil)))
> (def my-ref (ref #{}))
I get this error:
> IllegalArgumentException No value supplied for key
;>> (defn map-span [m f]
>>>(into {} (t/for [[k v] :- '[x y] m] :- '[x y1]
>>> [k (f v)])))
>>>
>>> Here's a real gist
>>> <https://gist.github.com/frenchy64/176fa8aadfd5b0cbfc09>.
>>>
>>> Thank
7;[x y] m] :- '[x y1]
>> [k (f v)])))
>>
>> Here's a real gist
>> <https://gist.github.com/frenchy64/176fa8aadfd5b0cbfc09>.
>>
>> Thanks,
>> Ambrose
>>
>> On Wed, Oct 15, 2014 at 2:28 PM, kurofune wrote:
>>
&g
y] m] :- '[x y1]
> [k (f v)])))
>
> Here's a real gist
> <https://gist.github.com/frenchy64/176fa8aadfd5b0cbfc09>.
>
> Thanks,
> Ambrose
>
> On Wed, Oct 15, 2014 at 2:28 PM, kurofune > wrote:
>
>> Hi everyone,
>>
>> I am learning
Hi,
The issue is that you can't use clojure.core/for in typed code.
You must use clojure.core.typed/for
<http://clojure.github.io/core.typed/#clojure.core.typed/for>, and annotate
the parameters and expected type.
(ann map-span (All [x y y1] [(Map x y) [y -> y1] -> (Map x y1)]
Hi everyone,
I am learning core.typed and ran into a stumbling block. When I use
annotations on normal functions and run 'check-ns', things work out ok,
;; works as expected
> (ann plus1 [Number -> Number])
> (defn plus1 [n] (+ n 1))
>
> ;; Works as expected
> (a
Thanks for the pointers, Ambrose, and thanks for core.typed!
James
On Thursday, 24 April 2014 17:24:21 UTC-4, Ambrose Bonnaire-Sergeant wrote:
>
> I haven't tried anything like this.
>
> The most obvious pitfall is core.typed currently loads lazily and collects
> type an
I haven't tried anything like this.
The most obvious pitfall is core.typed currently loads lazily and collects
type annotations only after check-ns.
There's a bunch of tools for manipulating types in the checker.
Thanks,
Ambrose
On Thu, Apr 24, 2014 at 11:18 PM, James MacAulay wro
I'm interested in exploring the use of the types provided by core.typed to
guide function behavior at runtime. Specifically, I'd like to wrap existing
functions such that the resulting functions behave in different ways
depending on the type signatures of each original function.
I&#
Great, thanks!
On Wed, Jan 29, 2014 at 1:54 AM, Sean Corfield wrote:
> I can confirm that I can evaluate namespaces that use core.typed 0.2.26
> inside LightTable - and run check-ns, which failed inside LightTable with
> 0.2.25!
>
> Sean
>
> On Jan 28, 2014, at 5:34
I can confirm that I can evaluate namespaces that use core.typed 0.2.26 inside
LightTable - and run check-ns, which failed inside LightTable with 0.2.25!
Sean
On Jan 28, 2014, at 5:34 AM, Ambrose Bonnaire-Sergeant
wrote:
> 0.2.26 contains a workaround by disabling the WIP Clojurescr
0.2.26 contains a workaround by disabling the WIP Clojurescript support.
You might need the
Sonatype<https://github.com/clojure/core.typed#releases-and-dependency-information>
repo.
I've got a GRE exam on Monday so I can't work on this properly yet.
Please let me know if it wo
Hi Ambrose,
Yes, I have a manual dependency on:
[org.clojure/clojurescript "0.0-2138"]
I looked at the project.clj of core.typed, and got:
https://github.com/clojure/core.typed/blob/master/project.clj#L13
Is the dependency on "[org.clojure/clojurescript "
Hi,
There is some conflict with ClojureScript, some others have also observed
this.
Is there some library that is upgrading the Clojurescript version to one
different to
what core.typed depends on?
Thanks,
Ambrose
On Tue, Jan 28, 2014 at 5:38 PM, t x wrote:
> ## Background
>
>
## Background
I'm using [org.clojure/core.typed "0.2.25"]
## Question:
Which is the following is true:
(1) my code is correct / should work, and therefore there is something
with my setup
(2) my code is wrong (and please point out how I can fix it)
## Code
(
On Sep 27, 2013, at 09:51, Ambrose Bonnaire-Sergeant wrote:
> I have started a crowdfunding campaign to support full-time work
> on Typed Clojure.
>
> Please share!
>
> http://www.indiegogo.com/projects/typed-clojure
With only five (5) days left, the Typed Clojure campaign still needs
$47,400 to
Hi,
Pleased to announce core.typed 0.2.14.
There are breaking changes in this release.
See the
Changelog<https://github.com/clojure/core.typed/blob/master/CHANGELOG.md>for
the full list of changes.
See the Readme <https://github.com/clojure/core.typed/blob/master/README.md>for
dep
Hi Stu,
Please try lein-typed "0.3.1". It should fix the build issue.
Thanks,
Ambrose
On Tue, Oct 1, 2013 at 8:42 AM, Ben Mabey wrote:
> Heh, based on that my guess is that no one has used lein-typed in CI
> builds. :) I've submitted a PR to Ambrose to exit with a non-zero code
> when type
Heh, based on that my guess is that no one has used lein-typed in CI
builds. :) I've submitted a PR to Ambrose to exit with a non-zero code
when type checking fails:
https://github.com/frenchy64/lein-typed/pull/1
Since lein-typed is brand new I imagine people have been writing there
own tasks
Any experience reports? My experience so far:
Type Checker: Found 1 error
$ echo $?
0
On Mon, Sep 30, 2013 at 7:20 PM, Ben Mabey wrote:
> On 9/30/13 5:16 PM, Stuart Halloway wrote:
>
>> I tried the following experiment with type checking clojure.set:
>>
>> (ns exploring.core-typed
>> (:us
On 9/30/13 5:16 PM, Stuart Halloway wrote:
I tried the following experiment with type checking clojure.set:
(ns exploring.core-typed
(:use clojure.core.typed clojure.repl)
(:require [clojure.set :as set]))
(ann ^:no-check clojure.set/difference [(Set Any) (Set Any) -> (Set Any)])
(set/diff
I tried the following experiment with type checking clojure.set:
(ns exploring.core-typed
(:use clojure.core.typed clojure.repl)
(:require [clojure.set :as set]))
(ann ^:no-check clojure.set/difference [(Set Any) (Set Any) -> (Set Any)])
(set/difference #{1 2} [1 2])
(comment
(check-ns)
Adam Bard has written an interesting blog post, comparing
core.typed to Haskell:
http://adambard.com/blog/core-typed-vs-haskell/
Both the post and the comments are worthwhile...
-r
--
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume r...@cfcl.com
http
The CircleCI folks have posted a nice write-up of Typed Clojure
(and the campaign) here:
tl;dr Typed Clojure is an important step for not just Clojure,
but all dynamic languages. CircleCI is supporting it, and you
should too.
Typed Clojure is one of the biggest advancements to dynamic
p
On Sep 27, 2013, at 09:51, Ambrose Bonnaire-Sergeant wrote:
> I have started a crowdfunding campaign to support full-time
> work on Typed Clojure.
>
> Please share!
>
> http://www.indiegogo.com/projects/typed-clojure
Still in its first day, the campaign is already an eighth
of the way to its goa
Hi,
I have started a crowdfunding campaign to support full-time work on Typed
Clojure.
Please share!
http://www.indiegogo.com/projects/typed-clojure
Thanks,
Ambrose
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send em
a particularly productive
> one for core.typed.
>
> In that time I:
>
> 1. released core.typed
> 0.2<https://groups.google.com/d/msg/clojure-core-typed/U_aA_Ce3qWg/gJWpdflBe4AJ>
> which
> I consider useful for production systems.
> 2. resolved 30 Ji
Hi,
Google Summer of Code has ended and it has been a particularly productive
one for core.typed.
In that time I:
1. released core.typed
0.2<https://groups.google.com/d/msg/clojure-core-typed/U_aA_Ce3qWg/gJWpdflBe4AJ>
which
I consider useful for production systems.
2. resolved 30 Jira
t
Thanks for all your work ambrose! Core.typed is quite a feat.
And I can confirm ambrose is amazingly responsive on freenode. Every time I
bug him, it works :)
On 10/09/2013 9:57 PM, "Ambrose Bonnaire-Sergeant" <
abonnaireserge...@gmail.com> wrote:
> Hi,
>
> Pushing anot
Hi,
Pushing another release of core.typed<https://github.com/clojure/core.typed>,
mostly bug/documentation fixes.
We now push a "slim" jar which does not include AOT file. See the README
for dependency information.
See the CHANGELOG for specific changes.
I'm also starting
Hi,
core.typed is designed to be used at the REPL.
Using core.typed at the
REPL<http://frenchy64.github.io/typed/clojure,/core.typed,/clojure/2013/09/03/core-typed-repl.html>
There is currently no automatic type checking when loading a namespace.
Consider a commented out
(check-ns), a uni
What's the compatibility with the REPL like? Is there anything like a
type-checked REPL initialization, or automatic type checking when loading a
namespace?
On Tuesday, 3 September 2013 11:18:04 UTC-7, Ambrose Bonnaire-Sergeant
wrote:
> Hi,
>
> Announcing lein typed, a tool to
intersection of easily and precisely typed, core.typed can save you a
lot of manual verification work!
As for the lein plugin, I think that low barriers to use will encourage
more people to try core.typed as a verification tool. My dream is to be
able to run a single command that infers a
Hi,
core.typed <https://github.com/clojure/core.typed> 0.2.3 is up, and comes
with two new functions:
- statistics<http://clojure.github.io/core.typed/#clojure.core.typed/statistics>
-
var-coverage<http://clojure.github.io/core.typed/#clojure.core.typed/var-coverage>
*statist
Released 0.2.0 which consolidates all commands to `lein typed check ...` on
advice of technomancy.
Thanks,
Ambrose
On Wed, Sep 4, 2013 at 2:18 AM, Ambrose Bonnaire-Sergeant <
abonnaireserge...@gmail.com> wrote:
> Hi,
>
> Announcing lein typed, a tool to use core.typed at t
Hi,
Just pushed core.typed 0.2.2. It should be significantly less
excruciating waiting for core.typed to initialise.
There are also minor documentation/error fixes.
[org.clojure/core.typed "0.2.2"]
...; for very recent releases:repositories {"sonatype-oss-public"
"
Hi,
Announcing lein typed, a tool to use core.typed at the command line.
https://github.com/frenchy64/lein-typed
Thanks,
Ambrose
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroup
Hi,
Some new posts on core.typed:
- Polymorphic
HOFs<http://frenchy64.github.io/typed/clojure,/core.typed,/clojure/2013/09/02/polymorphic-hof.html>
- Using core.typed at the
REPL<http://frenchy64.github.io/typed/clojure,/core.typed,/clojure/2013/09/03/core-typed-repl.html>
Also,
y to the thread. This release is pretty cool. I
> haven't been following the development too closely, so I have two questions:
>
> 1. Is ClojureScript/ClojureCLR supported by core.typed? Or, is it planned?
>
> 2. Is there a Leiningen plugin that can help run the type checks from the
Sorry for a late reply to the thread. This release is pretty cool. I
haven't been following the development too closely, so I have two questions:
1. Is ClojureScript/ClojureCLR supported by core.typed? Or, is it planned?
2. Is there a Leiningen plugin that can help run the type checks fro
Just pushed 0.2.1 based on feedback from the video on HN.
https://github.com/clojure/core.typed/blob/master/CHANGELOG.md
Thanks,
Ambrose
On Thu, Aug 29, 2013 at 6:28 AM, Ambrose Bonnaire-Sergeant <
abonnaireserge...@gmail.com> wrote:
> Hi,
>
> After 10 months and 26 0.
Yeah, it's pretty much impossible unless you limit yourself to a manageable
subset of Clojure. The "easy" part I was referring to was the Leiningen
plugin, not the whole kit n' caboodle.
On Thursday, August 29, 2013 11:02:17 AM UTC-5, Alex Baranosky wrote:
>
> Imo, there's nothing "easy" about
Imo, there's nothing "easy" about writing something like Slamhound. Even
after many iterations it can't handle macros, because ultimately they're
impossible, without some kind of hints specifically added for Slamhound (or
for Typed Clojure) :)
--
--
You received this message because you are subs
On Thu, Aug 29, 2013 at 5:01 PM, Ambrose Bonnaire-Sergeant
wrote:
> Well I'm sure people wouldn't be happy if their call to (+ a b c) was
> suddenly turned into (clojure.lang.Numbers/add (clojure.lang.Numbers/add a
> b) c)
>
> :)
the expresso [1] optimizer can be used for those optimizations ;)
. Typed Racket's "optimisation coach" comes to mind
>>>> in ways we can present this information ("put a type hint at line 10, col
>>>> 20 to get full speed...").
>>>>
>>>> Thanks,
>>>> Ambrose
>>>&g
formation ("put a type hint at line 10, col
>>> 20 to get full speed...").
>>>
>>> Thanks,
>>> Ambrose
>>>
>>>
>>> On Thu, Aug 29, 2013 at 6:03 PM, Christian Sperandio <
>>> christian...@gmail.com**> wrote:
>
t; Ambrose
>>
>>
>> On Thu, Aug 29, 2013 at 6:03 PM, Christian Sperandio <
>> christian...@gmail.com**> wrote:
>>
>>> Ok...
>>>
>>> Another question, the checking is done only once (while compiling) ? Or,
>>> it's done while the runtime?
>
e compiling) ? Or,
>> it's done while the runtime?
>>
>>
>>
>> 2013/8/29 Michael Klishin >
>>
>>> 2013/8/29 Christian Sperandio >
>>>
>>>> Is there any perf improvement to use static typing in Clojure?
>>&
g is done only once (while compiling) ? Or,
> it's done while the runtime?
>
>
>
> 2013/8/29 Michael Klishin
>
>> 2013/8/29 Christian Sperandio
>>
>>> Is there any perf improvement to use static typing in Clojure?
>>
>>
>> core.typed is n
Ok...
Another question, the checking is done only once (while compiling) ? Or,
it's done while the runtime?
2013/8/29 Michael Klishin
> 2013/8/29 Christian Sperandio
>
>> Is there any perf improvement to use static typing in Clojure?
>
>
> core.typed is n
2013/8/29 Christian Sperandio
> Is there any perf improvement to use static typing in Clojure?
core.typed is not a compiler, it's a type annotation/checker implemented
as a library.
If you are familiar with Erlang, it is to Clojure what Dialyzer is to
Erlang.
--
MK
http://gi
>> Hi,
>>
>> After 10 months and 26 0.1.x releases of transitioning core.typed from an
>> ambitious student project, I am finally comfortable recommending core.typed
>> for production use.
>>
>> Production Ready
>>
>> My interpretation of "
Congratulations and thanks for your work!
On Thursday, August 29, 2013 12:28:35 AM UTC+2, Ambrose Bonnaire-Sergeant
wrote:
>
> Hi,
>
> After 10 months and 26 0.1.x releases of transitioning core.typed from an
> ambitious student project, I am finally comfortable recommending co
Roughly 1/3 of clojure.core is annotated and comes included with
> core.typed. They are unchecked annotations.
>
>
> https://github.com/clojure/core.typed/blob/master/src/main/clojure/clojure/core/typed/base_env.clj#L658
>
> You can lookup types via cf at the REPL.
>
&
Hi,
Roughly 1/3 of clojure.core is annotated and comes included with
core.typed. They are unchecked annotations.
https://github.com/clojure/core.typed/blob/master/src/main/clojure/clojure/core/typed/base_env.clj#L658
You can lookup types via cf at the REPL.
(clojure.core.typed/cf +)
;=>
, but error messages will probably be unpredictable and unreadable, and
the type system would not have simple rules to get a namespace type
checking like Typed Clojure/Racket does. (eg. assign types to top-levels
and fn parameters.)
I'm fairly confident that if you use core.typed, you'll se
How about annotating clojure.core API. Is it needed, provided, optional?
On Thursday, August 29, 2013 12:28:35 AM UTC+2, Ambrose Bonnaire-Sergeant
wrote:
>
> Hi,
>
> After 10 months and 26 0.1.x releases of transitioning core.typed from an
> ambitious student project, I am fina
igning types to vars as it became evident that typing was needed as a
pre-runtime guardrail based on how other developers were using my functions.
If I'm publishing a library then that's backward thinking, but in a team using
core.typed it sounds useful... Only type what you need when yo
Hi Daniel,
It is unsound to assume we can pass anything to an unannotated, unchecked
var.
core.typed makes the user explicitly mark unchecked vars, which is also a
source of unsoundness, but an explicit one. Hopefully :no-check is not
ambiguous in this regard.
Take this example.
;; untyped
gt; Hi,
>
> After 10 months and 26 0.1.x releases of transitioning core.typed from an
> ambitious student project, I am finally comfortable recommending core.typed
> for production use.
>
> Production Ready
>
> My interpretation of "production ready" in this context is
Awesome. Thanks for your hard work!
Allen
On Wednesday, August 28, 2013 3:28:35 PM UTC-7, Ambrose Bonnaire-Sergeant
wrote:
>
> Hi,
>
> After 10 months and 26 0.1.x releases of transitioning core.typed from an
> ambitious student project, I am finally comfortable recommending co
Hi,
After 10 months and 26 0.1.x releases of transitioning core.typed from an
ambitious student project, I am finally comfortable recommending core.typed
for production use.
Production Ready
My interpretation of "production ready" in this context is:
- core.typed can *find bugs* in
Hi,
Announcing a new release of core.typed<https://github.com/clojure/core.typed>
.
[org.clojure/core.typed "0.1.24"]
There are some breaking changes surrounding the ann-{datatype,protocol}
macros, see the changelog and their corresponding var docs for the details.
We also no
0.1.20 is cut, the examples should work.
[org.clojure/core.typed "0.1.20"]
Also, you probably need to have (clojure.core.typed/typed-deps
clojure.core.typed.async) just below your ns form. core.typed doesn't seem
to infer the companion namespace sometimes.
Thanks,
Ambrose
On M
This release didn't quite go as planned. While trying release core.typed
without
a core.async dependency I managed to break support for core.async.
Fix coming.
Thanks,
Ambrose
On Sun, Aug 4, 2013 at 12:52 PM, Ambrose Bonnaire-Sergeant <
abonnaireserge...@gmail.com> wrote:
>
Hi,
This should be exciting news for some, and perhaps the last reason
to use Go for others ;)
core.typed now includes support for core.async.
- typed core.async
examples<https://github.com/clojure/core.typed/tree/master/examples/async>
.
- companion
namespace<https://github.co
ant <
abonnaireserge...@gmail.com> wrote:
> Hi,
>
> To mark the mid-GSoC evaluations, I'm happy to release another
> core.typed version.
>
> Highlights:
>
> - type checking speed enhancements
> - some usages of `every?` now update local types as expected
> - cu
Hi,
To mark the mid-GSoC evaluations, I'm happy to release another
core.typed version.
Highlights:
- type checking speed enhancements
- some usages of `every?` now update local types as expected
- currently works best on things exactly of type IPersistentCollection
(aka. a new alias Coll
Hi,
A brief but highly visible release of core.typed: types and forms in error
messages are abbreviated where possible.
See the changelog and check-ns docstring for details.
In a nutshell:
fire.main=> (check-ns 'fire.simulate)
...
Type Error (fire.simulate:72) Expected type: Gri
1 - 100 of 104 matches
Mail list logo
