Re: deprecation warnings?

You should! It will be the biggest and greatest CIDER release ever. It will likely be the most postponed release ever as well. :-) On 21 October 2015 at 04:42, James Elliott wrote: > Sweet, I’m starting to really look forward to that release. :D > > > On Monday, October 19,

Re: deprecation warnings?

Sweet, I’m starting to really look forward to that release. :D On Monday, October 19, 2015 at 10:54:04 AM UTC-5, Lars Andersen wrote: > > Font-locking of deprecated vars was just added to CIDER. It's available > in snapshots now, and will be included in 0.10. > > On Wednesday, October 14, 2015

Re: deprecation warnings?

Font-locking of deprecated vars was just added to CIDER. It's available in snapshots now, and will be included in 0.10. On Wednesday, October 14, 2015 at 6:09:21 PM UTC+2, William la Forge wrote: > > Going forward, I'd like to deprecate some functions and have a warning > displayed on first

Re: deprecation warnings?

Overkill for me right now. I need to delete the deprecated functions in the subsequent release anyway so this is a short-lived issue, this time at least. Plus, I suspect the aatree library is not yet in heavy use. (But I can dream, can't I?) I had looked at the defprecated project but it got

Re: deprecation warnings?

William la Forge wrote: Going forward, I'd like to deprecate some functions and have a warning displayed on first use. So I've done this: I use defprecate https://github.com/alexander-yakushev/defprecated -- You received this message because you are subscribed to the Google Groups "Clojure"

deprecation warnings?

Going forward, I'd like to deprecate some functions and have a warning displayed on first use. So I've done this: (def emptyAAMap ^{:deprecated "0.3.4"} (new AAMap emptyNode {:comparator RT/DEFAULT_COMPARATOR})) But I am not seeing any warnings from either lein or cursive. Do I need to add

Re: deprecation warnings?

Isn’t meta data before the symbol name? > On 14 Oct 2015, at 17:09, William la Forge wrote: > > Going forward, I'd like to deprecate some functions and have a warning > displayed on first use. So I've done this: > > (def emptyAAMap ^{:deprecated "0.3.4"} > (new AAMap

Re: deprecation warnings?

You might wish to up-vote http://dev.clojure.org/jira/browse/CLJ-706 -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient

Re: deprecation warnings?

OK, but 1. Still no warning from cursive or lein test and 2. I think the metadata goes after the arguments when defining multi-arity functions. On Wed, Oct 14, 2015 at 12:11 PM, Colin Yates wrote: > Isn’t meta data before the symbol name? > > On 14 Oct 2015, at 17:09,

Re: deprecation warnings?

Try out the Eastwood Clojure lint tool [1] and see if it gives deprecation warnings where you hope to see them. Andy [1] https://github.com/jonase/eastwood On Wed, Oct 14, 2015 at 9:31 AM, William la Forge <laforg...@gmail.com> wrote: > OK, but > > 1. Still no warning from cursi

Re: deprecation warnings?

*warn-on-deprecated* would be super! :D On Wed, Oct 14, 2015 at 1:44 PM, Alex Miller wrote: > You might wish to up-vote http://dev.clojure.org/jira/browse/CLJ-706 > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post

Re: deprecation warnings?

Sadly Cursive doesn't show this right now - it definitely should, though. Cheers, Colin On 15 October 2015 at 06:55, William la Forge wrote: > *warn-on-deprecated* would be super! :D > > On Wed, Oct 14, 2015 at 1:44 PM, Alex Miller wrote: > >> You