ClojureScript

clojure.reflect is asynchronous (should use CrossPageChannel)

Details

  • Type: Defect Defect
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

This makes printing at the REPL a bit annoying. We should be using the CrossPageChannel and not a ajax request to the built in webserver.

Activity

Hide
Brandon Bloom added a comment -

Was this ticket supposed to be filed against Clojure, not ClojureScript?

Show
Brandon Bloom added a comment - Was this ticket supposed to be filed against Clojure, not ClojureScript?
Hide
David Nolen added a comment -

No. This ticket refers to the HackerSchool work to provide a reflection hook for ClojureScript to make the REPL interactions more friendly. Look at clojure.reflect in the ClojureScript repo.

Show
David Nolen added a comment - No. This ticket refers to the HackerSchool work to provide a reflection hook for ClojureScript to make the REPL interactions more friendly. Look at clojure.reflect in the ClojureScript repo.
Hide
Frank Siebenlist added a comment -

As we've changed the topic of this issue a little bit..., I'd like to add the additional requirement that the reflection facility should be pluggable, meaning that if I have additional help/reflection functions that I want to make available to the cljs-repl users, then I should not have to wait for acceptance in a new clojurescript version.

Maybe some form of registration API thru which I can add new cljs-functions that communicate with their clj-counterparts thru some naming convention . Not sure about the details here...

Show
Frank Siebenlist added a comment - As we've changed the topic of this issue a little bit..., I'd like to add the additional requirement that the reflection facility should be pluggable, meaning that if I have additional help/reflection functions that I want to make available to the cljs-repl users, then I should not have to wait for acceptance in a new clojurescript version. Maybe some form of registration API thru which I can add new cljs-functions that communicate with their clj-counterparts thru some naming convention . Not sure about the details here...
Hide
David Nolen added a comment -

That's really a separate issue that probably warrants it's own discussion.

Show
David Nolen added a comment - That's really a separate issue that probably warrants it's own discussion.
Hide
Frank Siebenlist added a comment -

Well... you started to add the (seemingly unrelated) CrossPageChannel requirement to the asynchronous one

But seriously, the pluggability requirement is probably important to keep in mind when any implementation for asynchronous clojure/reflect is designed and implemented - I'll open-up another issue for pluggability to keep it clean.

Show
Frank Siebenlist added a comment - Well... you started to add the (seemingly unrelated) CrossPageChannel requirement to the asynchronous one But seriously, the pluggability requirement is probably important to keep in mind when any implementation for asynchronous clojure/reflect is designed and implemented - I'll open-up another issue for pluggability to keep it clean.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated: