Welcome! Please see the
About
page for a little more info on how this works.
GitHub Login
All Activity
Questions
Unanswered
Tags
Ask a Question
About
Ask a Question
compiled files with warnings that otherwise don't need recompilation will not emit warnings on the next compile
0
votes
asked
Mar 23, 2015
in
ClojureScript
by
jira
The aggressive caching approach is odds with warning visibility. It probably makes sense for a compiled file with warnings to always return {{true}} for {{requires-compilation?}}.
problem
jira
Please
log in
or
register
to add a comment.
Please
log in
or
register
to answer this question.
1
Answer
0
votes
answered
Jun 26, 2019
by
jira
Reference:
https://clojure.atlassian.net/browse/CLJS-1159
(reported by dnolen)
Please
log in
or
register
to add a comment.
Welcome to Clojure Q&A, where you can ask questions and receive answers from members of the Clojure community.
Related questions
Don't log deprecation warnings on recursive calls to the same function with a different arity
clojure.walk.macroexpand-all will not properly expand macros that depend on &env
Sorted colls with default comparator don't check that first element is Comparable
cljsc.bat emit FileNotFoundException when compile samples in windows
`clojure.string/split` with a limit can not correctly split a string by a regular expression that using Lookahead or Loo
Categories
All categories
Clojure
(1.5k)
ClojureScript
(612)
ClojureCLR
(26)
Contrib libs
(726)
Tools
(74)
Meta
(19)
Other
(93)
...