Slipway is a Clojure Companion to Jetty.

I'm not much of a regular on this slack but I'll check back in this thread later on to answer questions if there are any. Ta.

How does this companionship work? The README doesn't describe anything useful in one sentence. So is it a configuration helper or is it some kind of a separate UI tool? There is a UI so why do you need it if it's a config helper? Is it a UI server configuration tool? Is there a simple way to understand what it accomplishes?

Also this post should've probably be posted into #announcements instead.

You can write (.-conf this) to access the conf field of a record in the default-implementation map.

ohhhh

I am going to try that out, thanks!

also ... you have some missing ) in the code you posted

(defprotocol TestProtocol
  (getFile [this])
  (getName [this]))

(defrecord TestRecord [conf])

(def default-implementation
  {:getFile (fn [this] (:file (.-conf this)))
   :getName (fn [this] (:name (.-conf this)))})

(extend TestRecord TestProtocol default-implementation)

(getFile (TestRecord. {:file "filename" :name "Bob Dabolina"})) ;; => "filename"

It works! Do you have any idea how and if reflection can be avoided here?

Btw, same guy, different username idk why

I might need to add type hint or just use a keywordized version of the field name, it should work as well

@U0P0TMEFJ thanks for your help, it worked and I am now able to do what I wanted 🙂

Just doing (:conf this) didn't work? It should work, and it is preferable over using the interop syntax when working with records.

Like this should work:

(def default-implementation
  {:getFile (fn [this] (-> this :conf :file))
   :getName (fn [this] (-> this :conf :name))})

this refers to the record, and you can use it like you would use the record anywhere, which is normally to treat it like a map.

Tested this in 1.11.1 and 1.12.0-alpha1

probably a bug - put it on http://ask.clojure.org

I know we have https://clojure.atlassian.net/browse/CLJ-2126 in the 1.12 list which is in this ballpark (but kind of the opposite)

I added it at http://ask.clojure.org and referred to David's bug report at ClojureCLR atlassian: https://clojure.atlassian.net/browse/CLJCLR-122

my guess is that this is a by-product of https://clojure.atlassian.net/browse/CLJ-1472

The compiler will often hoist things like try/catch into immediately invoked anonymous functions, easiest way to give expression like semantics to more complex bytecode

I'm quite relieved to learn that CLJCLR-122 is also a problem over on the JVM, in the hope that someone else will solve the problem before I have to. (The immediate locus of the problem is at the ClojureCLr equivalent to https://github.com/clojure/clojure/blob/527b330045ef35b47a968d80ed3dc4999cfa2623/src/jvm/clojure/lang/Compiler.java#L4943 , but the most obvious fix at that location does not work.) (In contrast, CLJ-2126 is not a problem for ClojureCLR; I think this is called a 'happy accident'.)

It turns out that try is sufficient, even without a finally.

(deftype T [^:volatile-mutable x] 
   P 
   (f []  
     (try 
       (set! x 7) 
       (prn ""))))

(deftype T [^:volatile-mutable x] 
   P 
   (f []  
     (try 
       (set! x 7))
     (prn ""))))

I tracked down the cause. Comment added to the CLJ-2743. The cause was code added in 2008.

I just ran into this using binding too https://clojurians.slack.com/archives/C03S1KBA2/p1672167142121029