emezeske/lein-cljsbuild

org.clojure.core.rrb-vector errors

Open

#469 opened on Aug 16, 2017

View on GitHub
 (6 comments) (6 reactions) (0 assignees)Clojure (1,096 stars) (153 forks)batch import
BugHelp WantedSuccessful Repro

Description

There is a problem compiling with respect to the "ranges" macro, which conflicts with a function name. Building with ClojureScript's public API directly compiles just fine.

clojure.lang.ExceptionInfo: failed compiling file:target/js/clojure/core/rrb_vector/trees.cljs {:file #object[java.io.File 0x6a65daed "target/js/clojure/core/rrb_vector/trees.cljs"]}
....
Caused by: clojure.lang.ArityException: Wrong number of args (1) passed to: nodes/ranges
        at cljs.analyzer$macroexpand_1_STAR_$fn__2179.invoke(analyzer.cljc:2658)
....

See full details in original discussion: https://github.com/brandonbloom/fipp/issues/42

Here's a diff to the RRB vector project that works around this problem: https://github.com/clojure/core.rrb-vector/compare/master...alexandergunnarson:master

Contributor guide

Tech stack
None
Domain
build systemtooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
ClojureScript basicsleiningen build tool
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue arises from a macro name conflict in clojure.core.rrb vector where the 'ranges' macro clashes with a function. The error occurs during compilation with lein cljsbuild. A workaround diff is provided in the core.rrb vector project. The fix likely involves renaming the macro or adjusting the compilation order. Investigate the referenced diff and the linked discussion (https://github.com/brandonbloom/fipp/issues/42) to understand the proper resolution.