defrecord can't impl some interface methods

2018-07-04 Thread Leon Grapenthin 
IDK if it has always been this case, but this doesn't compile in Clojure 1.9

(defprotocol Cleanable (clean [this]))

(defrecord Cleaner [] Cleanable (clean [this] "cleaned!"))

This is likely because java.util.Map implements a clean method with the 
same amount of args (0) and defrecord somehow also implements java.util.Map.

Is this intended or ticket-worthy?

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How do I use spec and deftype together?

2018-07-04 Thread markus . agwin 
The same question was asked on
https://clojurians-log.clojureverse.org/clojure-spec/2018-01-19
but I did not find an answer.

An example, where defrecord works fine but deftype fails:

(do
  (require '[clojure.spec.alpha :as s])
  (defprotocol Foo (foo [this]))
  (defrecord Bar [bar] Foo (foo [this] (.bar this)))
  (deftype   Baz [bar] Foo (foo [this] (.bar this)))
  (s/def ::bar number?)
  [(s/valid? (s/keys :req-un [::bar]) (->Bar 0))
   (s/valid? (s/keys :req-un [::bar]) (->Baz 0))]) ;[true false]


How do I have to change the last line so that it yields true as well?

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I use spec and deftype together?

2018-07-04 Thread Leon Grapenthin 
Spec doesn't check object fields. The defrecord case works because 
defrecord implements map.

On Wednesday, July 4, 2018 at 12:47:26 PM UTC+2, markus...@gmail.com wrote:
>
> The same question was asked on
> https://clojurians-log.clojureverse.org/clojure-spec/2018-01-19
> but I did not find an answer.
>
> An example, where defrecord works fine but deftype fails:
>
> (do
>   (require '[clojure.spec.alpha :as s])
>   (defprotocol Foo (foo [this]))
>   (defrecord Bar [bar] Foo (foo [this] (.bar this)))
>   (deftype   Baz [bar] Foo (foo [this] (.bar this)))
>   (s/def ::bar number?)
>   [(s/valid? (s/keys :req-un [::bar]) (->Bar 0))
>(s/valid? (s/keys :req-un [::bar]) (->Baz 0))]) ;[true false]
>
>
> How do I have to change the last line so that it yields true as well?
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What is the minimal Emacs config for practical Clojure development?

2018-07-04 Thread Łukasz Korecki 
On Tuesday, July 3, 2018 at 4:46:05 PM UTC+1, Austin Haas wrote:
>
> Thanks for the replies. 
>
> I only want a stable REPL, integrated with Emacs, and nothing else. 
>
> Łukasz, why did you switch to Monroe? What do you prefer about it?


If I'm not mistaken inf-clojure works best if you use the socket REPL. 
All our projects have a nREPL server embedded so  Monroe was a better fit 
for my workflow.

Nothing against inf-clojure, it works great!

Łukasz

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I use spec and deftype together?

2018-07-04 Thread markus . agwin 
So is it best practice to implement map in the deftype to make it 
spec-able? Are there examples somewhere that show how to do this in a 
canonical way?

On Wednesday, July 4, 2018 at 12:51:29 PM UTC+2, Leon Grapenthin wrote:
>
> Spec doesn't check object fields. The defrecord case works because 
> defrecord implements map.
>
> On Wednesday, July 4, 2018 at 12:47:26 PM UTC+2, markus...@gmail.com 
> wrote:
>>
>> The same question was asked on
>> https://clojurians-log.clojureverse.org/clojure-spec/2018-01-19
>> but I did not find an answer.
>>
>> An example, where defrecord works fine but deftype fails:
>>
>> (do
>>   (require '[clojure.spec.alpha :as s])
>>   (defprotocol Foo (foo [this]))
>>   (defrecord Bar [bar] Foo (foo [this] (.bar this)))
>>   (deftype   Baz [bar] Foo (foo [this] (.bar this)))
>>   (s/def ::bar number?)
>>   [(s/valid? (s/keys :req-un [::bar]) (->Bar 0))
>>(s/valid? (s/keys :req-un [::bar]) (->Baz 0))]) ;[true false]
>>
>>
>> How do I have to change the last line so that it yields true as well?
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I use spec and deftype together?

2018-07-04 Thread markus . agwin 
So is it best practice to implement map in the deftype to make it 
spec-able? Are there examples somewhere that show how to do this in a 
canonical way?

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [ANN] Clojure 1.10.0-alpha5

2018-07-04 Thread Sean Corfield 
I happened to notice this morning that the patch for CLJ-2367 was merged and 
Clojure 1.10.0-alpha6 has quietly gone up to Maven Central so we’re running a 
full pass of our tests at work on the new ASM/Java 8+ stuff.

The 1.10.0-master-SNAPSHOT is currently lagging behind (June 27) and does not 
yet include this fix.

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


From: Sean Corfield 
Sent: Thursday, June 28, 2018 4:26:36 PM
To: clojure@googlegroups.com
Subject: RE: [ANN] Clojure 1.10.0-alpha5

Anyone using taoensso/nippy will encounter a compilation exception on Clojure 
1.10.0 Alpha 5. See https://dev.clojure.org/jira/browse/CLJ-2367 for details 
(an unexpected – and probably unintended – change in the new ASM 
GeneratorAdapter breaks casts from short or byte to int).

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


From: clojure@googlegroups.com  on behalf of Alex 
Miller 
Sent: Wednesday, June 27, 2018 12:52:20 PM
To: Clojure
Subject: [ANN] Clojure 1.10.0-alpha5

Clojure 1.10.0-alpha5 is now available.

1.10.0-alpha5 includes the following changes since 1.10.0-alpha4:

* CLJ-2363 - make Java 8 the 
minimum requirement for Clojure (also bumps embedded ASM to latest) - thanks 
Ghadi Shayban!
* CLJ-2284 - fix invalid bytecode 
generation for static interface method calls in Java 9+ - thanks Ghadi Shayban!
* CLJ-2330 - fix brittle test 
that fails on Java 10 build due to serialization drift
* CLJ-2362 - withMeta() should 
return identity when new meta is identical to prior
* CLJ-1130 - when unable to match 
static method, improve error messages
* CLJ-2089 - sorted colls with 
default comparator don't check that first element is Comparable
* CLJ-2163 - add test for var 
serialization
* Bump dependency version for spec.alpha to latest, 0.2.168 (see 
changes)
* Bump dependency version for core.specs.alpha to latest, 0.2.36 (see 
changes)

NOTE: 1.10.0-alpha5 drops support for Java 6 and 7 and makes Java 8 the minimum 
requirement. Compilation will produce Java 8 level bytecode (which will not run 
on earlier versions of Java). This is the first change in bytecode version 
since Clojure 1.6. We would greatly appreciate it if you tried this release 
with your library or project and provided feedback about errors, performance 
differences (good or bad), compatibility, etc.

When using the `clj` tool and deps.edn, we recommend adding an alias to your 
~/.clojure/deps.edn:

{:aliases
 {:clj/next
  {:override-deps
   {org.clojure/clojure {:mvn/version "1.10.0-alpha5"}

You can then run any of your projects with the latest Clojure dev release by 
activating the alias with `clj`:

  clj -A:clj/next



--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: How do I use spec and deftype together?

2018-07-04 Thread Sean Corfield 
So is it best practice to implement map in the deftype to make it spec-able? 
Are there examples somewhere that show how to do this in a canonical way?

If you want a `deftype` that is spec-able as a map, why not just use 
`defrecord`? Manually implementing the various map-related interfaces is a fair 
bit of boilerplate/work.

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


From: clojure@googlegroups.com  on behalf of 
markus.ag...@gmail.com 
Sent: Wednesday, July 4, 2018 7:47:45 AM
To: Clojure
Subject: Re: How do I use spec and deftype together?

So is it best practice to implement map in the deftype to make it spec-able? 
Are there examples somewhere that show how to do this in a canonical way?

On Wednesday, July 4, 2018 at 12:51:29 PM UTC+2, Leon Grapenthin wrote:
Spec doesn't check object fields. The defrecord case works because defrecord 
implements map.

On Wednesday, July 4, 2018 at 12:47:26 PM UTC+2, markus...@gmail.com wrote:
The same question was asked on
https://clojurians-log.clojureverse.org/clojure-spec/2018-01-19
but I did not find an answer.

An example, where defrecord works fine but deftype fails:

(do
  (require '[clojure.spec.alpha :as s])
  (defprotocol Foo (foo [this]))
  (defrecord Bar [bar] Foo (foo [this] (.bar this)))
  (deftype   Baz [bar] Foo (foo [this] (.bar this)))
  (s/def ::bar number?)
  [(s/valid? (s/keys :req-un [::bar]) (->Bar 0))
   (s/valid? (s/keys :req-un [::bar]) (->Baz 0))]) ;[true false]

How do I have to change the last line so that it yields true as well?

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Clojure 1.10.0-alpha5

2018-07-04 Thread Alex Miller 
The snapshots run nightly.

> On Jul 4, 2018, at 1:23 PM, Sean Corfield  wrote:
> 
> I happened to notice this morning that the patch for CLJ-2367 was merged and 
> Clojure 1.10.0-alpha6 has quietly gone up to Maven Central so we’re running a 
> full pass of our tests at work on the new ASM/Java 8+ stuff.
>  
> The 1.10.0-master-SNAPSHOT is currently lagging behind (June 27) and does not 
> yet include this fix.
>  
> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
> An Architect's View -- http://corfield.org/
> 
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>  
> From: Sean Corfield 
> Sent: Thursday, June 28, 2018 4:26:36 PM
> To: clojure@googlegroups.com
> Subject: RE: [ANN] Clojure 1.10.0-alpha5
>  
> Anyone using taoensso/nippy will encounter a compilation exception on Clojure 
> 1.10.0 Alpha 5. See https://dev.clojure.org/jira/browse/CLJ-2367 for details 
> (an unexpected – and probably unintended – change in the new ASM 
> GeneratorAdapter breaks casts from short or byte to int).
>  
> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
> An Architect's View -- http://corfield.org/
> 
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>  
> From: clojure@googlegroups.com  on behalf of Alex 
> Miller 
> Sent: Wednesday, June 27, 2018 12:52:20 PM
> To: Clojure
> Subject: [ANN] Clojure 1.10.0-alpha5
>  
> Clojure 1.10.0-alpha5 is now available.
> 
> 1.10.0-alpha5 includes the following changes since 1.10.0-alpha4:
> 
> * CLJ-2363 - make Java 8 the minimum requirement for Clojure (also bumps 
> embedded ASM to latest) - thanks Ghadi Shayban!
> * CLJ-2284 - fix invalid bytecode generation for static interface method 
> calls in Java 9+ - thanks Ghadi Shayban!
> * CLJ-2330 - fix brittle test that fails on Java 10 build due to 
> serialization drift
> * CLJ-2362 - withMeta() should return identity when new meta is identical to 
> prior
> * CLJ-1130 - when unable to match static method, improve error messages
> * CLJ-2089 - sorted colls with default comparator don't check that first 
> element is Comparable
> * CLJ-2163 - add test for var serialization
> * Bump dependency version for spec.alpha to latest, 0.2.168 (see changes)
> * Bump dependency version for core.specs.alpha to latest, 0.2.36 (see changes)
> 
> NOTE: 1.10.0-alpha5 drops support for Java 6 and 7 and makes Java 8 the 
> minimum requirement. Compilation will produce Java 8 level bytecode (which 
> will not run on earlier versions of Java). This is the first change in 
> bytecode version since Clojure 1.6. We would greatly appreciate it if you 
> tried this release with your library or project and provided feedback about 
> errors, performance differences (good or bad), compatibility, etc.
> 
> When using the `clj` tool and deps.edn, we recommend adding an alias to your 
> ~/.clojure/deps.edn:
> 
> {:aliases
>  {:clj/next
>   {:override-deps
>{org.clojure/clojure {:mvn/version "1.10.0-alpha5"}
>  
> You can then run any of your projects with the latest Clojure dev release by 
> activating the alias with `clj`: 
> 
>   clj -A:clj/next
> 
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with your 
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> -- 
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with your 
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Clojure" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/clojure/ESNrjIr0JUE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr.

Re: [ANN] Clojure 1.10.0-alpha5

2018-07-04 Thread Alex Miller 
And they also run on commit if we don’t force a release before that happens.

> On Jul 4, 2018, at 2:15 PM, Alex Miller  wrote:
> 
> The snapshots run nightly.
> 
>> On Jul 4, 2018, at 1:23 PM, Sean Corfield  wrote:
>> 
>> I happened to notice this morning that the patch for CLJ-2367 was merged and 
>> Clojure 1.10.0-alpha6 has quietly gone up to Maven Central so we’re running 
>> a full pass of our tests at work on the new ASM/Java 8+ stuff.
>>  
>> The 1.10.0-master-SNAPSHOT is currently lagging behind (June 27) and does 
>> not yet include this fix.
>>  
>> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
>> An Architect's View -- http://corfield.org/
>> 
>> "If you're not annoying somebody, you're not really alive."
>> -- Margaret Atwood
>>  
>> From: Sean Corfield 
>> Sent: Thursday, June 28, 2018 4:26:36 PM
>> To: clojure@googlegroups.com
>> Subject: RE: [ANN] Clojure 1.10.0-alpha5
>>  
>> Anyone using taoensso/nippy will encounter a compilation exception on 
>> Clojure 1.10.0 Alpha 5. See https://dev.clojure.org/jira/browse/CLJ-2367 for 
>> details (an unexpected – and probably unintended – change in the new ASM 
>> GeneratorAdapter breaks casts from short or byte to int).
>>  
>> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
>> An Architect's View -- http://corfield.org/
>> 
>> "If you're not annoying somebody, you're not really alive."
>> -- Margaret Atwood
>>  
>> From: clojure@googlegroups.com  on behalf of Alex 
>> Miller 
>> Sent: Wednesday, June 27, 2018 12:52:20 PM
>> To: Clojure
>> Subject: [ANN] Clojure 1.10.0-alpha5
>>  
>> Clojure 1.10.0-alpha5 is now available.
>> 
>> 1.10.0-alpha5 includes the following changes since 1.10.0-alpha4:
>> 
>> * CLJ-2363 - make Java 8 the minimum requirement for Clojure (also bumps 
>> embedded ASM to latest) - thanks Ghadi Shayban!
>> * CLJ-2284 - fix invalid bytecode generation for static interface method 
>> calls in Java 9+ - thanks Ghadi Shayban!
>> * CLJ-2330 - fix brittle test that fails on Java 10 build due to 
>> serialization drift
>> * CLJ-2362 - withMeta() should return identity when new meta is identical to 
>> prior
>> * CLJ-1130 - when unable to match static method, improve error messages
>> * CLJ-2089 - sorted colls with default comparator don't check that first 
>> element is Comparable
>> * CLJ-2163 - add test for var serialization
>> * Bump dependency version for spec.alpha to latest, 0.2.168 (see changes)
>> * Bump dependency version for core.specs.alpha to latest, 0.2.36 (see 
>> changes)
>> 
>> NOTE: 1.10.0-alpha5 drops support for Java 6 and 7 and makes Java 8 the 
>> minimum requirement. Compilation will produce Java 8 level bytecode (which 
>> will not run on earlier versions of Java). This is the first change in 
>> bytecode version since Clojure 1.6. We would greatly appreciate it if you 
>> tried this release with your library or project and provided feedback about 
>> errors, performance differences (good or bad), compatibility, etc.
>> 
>> When using the `clj` tool and deps.edn, we recommend adding an alias to your 
>> ~/.clojure/deps.edn:
>> 
>> {:aliases
>>  {:clj/next
>>   {:override-deps
>>{org.clojure/clojure {:mvn/version "1.10.0-alpha5"}
>>  
>> You can then run any of your projects with the latest Clojure dev release by 
>> activating the alias with `clj`: 
>> 
>>   clj -A:clj/next
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clojure@googlegroups.com
>> Note that posts from new members are moderated - please be patient with your 
>> first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clojure@googlegroups.com
>> Note that posts from new members are moderated - please be patient with your 
>> first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Clojure" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/clojure/ESNrjIr0JUE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to

Re: defrecord can't impl some interface methods

2018-07-04 Thread OHTA Shogo 
Seems like it's already reported on JIRA a couple of years ago: 
https://dev.clojure.org/jira/browse/CLJ-1791

On Wednesday, July 4, 2018 at 6:58:13 PM UTC+9, Leon Grapenthin wrote:
>
> IDK if it has always been this case, but this doesn't compile in Clojure 
> 1.9
>
> (defprotocol Cleanable (clean [this]))
>
> (defrecord Cleaner [] Cleanable (clean [this] "cleaned!"))
>
> This is likely because java.util.Map implements a clean method with the 
> same amount of args (0) and defrecord somehow also implements java.util.Map.
>
> Is this intended or ticket-worthy?
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.