Private access of


  • Type: Enhancement Enhancement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Completed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:


In there are 3 accesses of, which is private.

The accesses are on line 93, 99, and 110. Here is the first for reference:

(This is detectable with work in progress in CLJS-1702.)

This ticket essentially asks for these 3 accesses to be addressed so that they don't trigger spurious warnings if and when CLJS-1702 is ultimately shipped.

Using #'char-code would prevent the private var access warnings (as it would with Clojure). If that kind of revision is undesirable (from a performance standpoint), and also making a copy of that utility function into the namespace is undesired, one potential third avenue of "addressing" this would be the possibility that CLJS-1702 would introduce new metadata that can be placed on the symbols in order to simply suppress the ClojureScript analyzer warnings without otherwise affecting the generated code.

That third avenue, which would need to await the outcome of CLJS-1702 (to be sure that metadata will indeed be used, and for the final name of the metadata), would involve code that looks something like this

(^:private-var-access-nowarn char-code (nth token i) base)


Vote (0)
Watch (0)


  • Created: