I'll do you one better... instead of having a convention for the value of
the :deprecated key, use a map so you can have information such as the
version in which it was deprecated, planned removal version, alternatives
and soforth.
On Thursday, August 11, 2016 at 1:54:08 AM UTC-7, Matt Mower wrote:
>
> On Wednesday, 10 August 2016 13:22:47 UTC+1, Alex Miller wrote:
>
>> In this case, there is not a specific function to point to, rather the
>> use of a transducer with a chan is the alternative.
>
>
> How about {:deprecated <url>} where the URL could refer to a
> human-readable/machine-processable description of the deprecation and
> alternative that could be presented by a tool/IDE.
>
> m/
>
--
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 with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
