This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-09
Channels
- # announcements (6)
- # babashka (17)
- # beginners (70)
- # calva (6)
- # chlorine-clover (88)
- # cider (9)
- # cljs-dev (9)
- # clojure (66)
- # clojure-australia (3)
- # clojure-czech (5)
- # clojure-europe (73)
- # clojure-nl (5)
- # clojure-spec (62)
- # clojure-uk (38)
- # clojurescript (30)
- # cursive (10)
- # datomic (16)
- # events (1)
- # figwheel-main (1)
- # fulcro (6)
- # graphql (21)
- # helix (4)
- # jackdaw (1)
- # jobs-rus (1)
- # kaocha (3)
- # luminus (11)
- # malli (28)
- # pedestal (3)
- # re-frame (2)
- # reagent (3)
- # sci (2)
- # shadow-cljs (21)
- # spacemacs (2)
- # sql (25)
- # timbre (2)
- # tools-deps (9)
- # tree-sitter (1)
- # xtdb (21)
morning
Morning
Morning
mĂĄnmĂĄn
they have slightly different capabilities iirc - proxy lets you extend an abstract class, reify is interface only. i tend to use reify more, but that's probably because i'm more often implementing a protocol than extending an abstract class. i've no idea if one is "better" than the other for just implementing java interfaces
Here's another question, say you have an interface with, say 5 methods, with reify, do you have to provide implementations for both, or can you implement one and ignore the rest?
user=> (definterface i (f []) (g []))
user.i
user=> (.f (reify i (f [_] 1)))
1
user=> (.g (reify i (f [_] 1)))
Execution error (AbstractMethodError) at user/eval157 (REPL:1).
user$eval157$reify__158.g()Ljava/lang/Object;
AFAIK you need to implement them all. You could probably give them no-op implementations, though
That’s a profound question. Is 20% of a bird a bird? Depends on the use-case I suppose 🙂
I had roast chicken last night. Perhaps about 20% of that chicken was consumed 🙂
<delurk> I take the view that an interface is a contract. “Implement these methods and then your reified class satisfies the contract (and is a bird or whatever).” If you don’t implement all of them then you don’t comply
anyone here using clojurescript with react-native atm ? what's the best toolchain now ?
@mccraigmccraig cordova finally crossed you for the last time?
@alex.lynham pretty much. insufficient community energy behind it, too few plugins with too low quality
the question is how long before react becomes the rails of the JS world
would that be a good thing? i liked rails - wasn't so fond of ruby tho
think i was the opposite, quite liked ruby, came to resent rails
either way i just mean in terms of 'becomes the one way to do things, then becomes obsolete'
but i spose that happens to everything
maybe i stopped using rails before obsolescence set it... ruby's awful scoping and bad-magic metaprogramming facilities really did my head in though
yeah the metaprogramming got p wild and unmaintainable p fast
Someone pointed me to this today: https://devdocs.io/