<!--
RSS generated by JIRA (4.4#649-r158309) at Sun May 26 00:26:57 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://dev.clojure.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+10010+AND+labels+%3D+metadata&tempMax=1000&field=key&field=summary
-->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
<?xml-stylesheet href="http://dev.clojure.org/jira/styles/jiraxml2html.xsl" type="text/xsl"?>
-->
<rss version="0.92">
    <channel>
        <title>Clojure JIRA</title>
        <link>http://dev.clojure.org/jira/secure/IssueNavigator.jspa?reset=true&amp;jqlQuery=project+%3D+10010+AND+labels+%3D+metadata</link>
        <description>An XML representation of a search request</description>
                <language>en-us</language>
                        <issue start="0" end="2" total="2"/>
                <build-info>
            <version>4.4</version>
            <build-number>649</build-number>
            <build-date>25-07-2011</build-date>
        </build-info>
<item>
            <title>[CLJ-918] Vars with {:macro true} meta data do not work when loaded from AOT compiled file</title>
                <link>http://dev.clojure.org/jira/browse/CLJ-918</link>
                <project id="10010" key="CLJ">Clojure</project>
                        <description>&lt;p&gt;When defining a var with &lt;tt&gt;^{:macro true&lt;/tt&gt;} the call of the binded macro does emit a warning when the definition has been AOT compiled.&lt;/p&gt;

&lt;p&gt;See example outputs with demo code here: &lt;a href=&quot;https://refheap.com/paste/389&quot;&gt;https://refheap.com/paste/389&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Bronsa on #clojure created a patch: &lt;a href=&quot;http://sprunge.us/bWcc&quot;&gt;http://sprunge.us/bWcc&lt;/a&gt;&lt;/p&gt;</description>
                <environment>Tested with 1.3.0 and 1.4.0</environment>
            <key id="15145">CLJ-918</key>
            <summary>Vars with {:macro true} meta data do not work when loaded from AOT compiled file</summary>
                <type id="4" iconUrl="http://dev.clojure.org/jira/images/icons/improvement.gif">Enhancement</type>
                                <priority id="5" iconUrl="http://dev.clojure.org/jira/images/icons/priority_trivial.gif">Trivial</priority>
                    <status id="6" iconUrl="http://dev.clojure.org/jira/images/icons/status_closed.gif">Closed</status>
                    <resolution id="3">Duplicate</resolution>
                                <assignee username="-1">Unassigned</assignee>
                                <reporter username="jannschu">Jannik Schorg</reporter>
                        <labels>
                        <label>Compiler</label>
                        <label>enhancement</label>
                        <label>metadata</label>
                    </labels>
                <created>Mon, 23 Jan 2012 16:06:06 -0600</created>
                <updated>Thu, 13 Sep 2012 14:29:01 -0500</updated>
                    <resolved>Thu, 13 Sep 2012 14:29:01 -0500</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="29437" author="jafingerhut" created="Thu, 13 Sep 2012 14:29:01 -0500"  >&lt;p&gt;Duplicate of &lt;a href=&quot;http://dev.clojure.org/jira/browse/CLJ-1021&quot; title=&quot;(let [i 5] (defmacro m [v] v) m) interprets m as a function, not a macro&quot;&gt;CLJ-1021&lt;/a&gt;.  Later ticket kept in preference to this one, because it has a patch and this one does not.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Patch</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10010">New</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                        </customfields>
    </item>

<item>
            <title>[CLJ-916] into loses metadata</title>
                <link>http://dev.clojure.org/jira/browse/CLJ-916</link>
                <project id="10010" key="CLJ">Clojure</project>
                        <description>&lt;p&gt;The into fn loses metadata.&lt;/p&gt;

&lt;p&gt;I&apos;m seeing some team members (myself included) rely on metadata. Metadata has been incredibly useful in some cases, however the silent destruction of metadata by core clojure fns (into, walk, etc) have been a source of increasing complexity and confusion. &lt;/p&gt;

&lt;p&gt;A team member could start relying on a 3rd party library that used &apos;into&apos;. Actually, the into fn could essentially be added to the code base at any time in many ways. Wrt metadata the potential for incidental complexity increases exponentially as more developers and libraries enter the mix. &lt;/p&gt;

&lt;p&gt;One of the reasons Clojure has worked for us so well is because it has greatly reduced incidental complexity.&lt;br/&gt;
IMHO the &apos;into metadata bug&apos; seriously limits the usefulness of metadata and would love to see the into fn fixed in 1.4.&lt;/p&gt;



</description>
                <environment></environment>
            <key id="15134">CLJ-916</key>
            <summary>into loses metadata</summary>
                <type id="1" iconUrl="http://dev.clojure.org/jira/images/icons/bug.gif">Defect</type>
                                <priority id="3" iconUrl="http://dev.clojure.org/jira/images/icons/priority_major.gif">Major</priority>
                    <status id="6" iconUrl="http://dev.clojure.org/jira/images/icons/status_closed.gif">Closed</status>
                    <resolution id="1">Completed</resolution>
                                <assignee username="-1">Unassigned</assignee>
                                <reporter username="markswanson">Mark Swanson</reporter>
                        <labels>
                        <label>into</label>
                        <label>metadata</label>
                        <label>walk</label>
                    </labels>
                <created>Sat, 21 Jan 2012 11:58:29 -0600</created>
                <updated>Sat, 18 Aug 2012 07:50:41 -0500</updated>
                    <resolved>Sat, 18 Aug 2012 07:50:41 -0500</resolved>
                            <version>Release 1.3</version>
                                <fixVersion>Release 1.5</fixVersion>
                                        <due></due>
                    <votes>4</votes>
                        <watches>5</watches>
                        <comments>
                    <comment id="27899" author="jafingerhut" created="Thu, 1 Mar 2012 04:42:26 -0600"  >&lt;p&gt;Someone please correct this if it is wrong, but it seems that into loses metadata because it is implemented using transients, and transients lose metadata.  If true, then one way to fix this ticket is to implement metadata for transients.&lt;/p&gt;

&lt;p&gt;Are there any fundamental reasons why it would be difficult to add metadata to transients, as long as the metadata itself was immutable?&lt;/p&gt;</comment>
                    <comment id="27958" author="jafingerhut" created="Fri, 16 Mar 2012 04:57:42 -0500"  >&lt;p&gt;First rough cut of a patch that makes not only into, but also select-keys, clojure.set/project, and clojure.set/rename preserve metadata.  Added tests for these and many other functions.  Still some open questions about other functions not tested in comments.  This patch does not attempt to make transients preserve metadata.&lt;/p&gt;</comment>
                    <comment id="28001" author="jafingerhut" created="Fri, 23 Mar 2012 20:03:25 -0500"  >&lt;p&gt;clj-916-make-into-and-others-preserve-metadata-patch2.txt is semantically same patch and comments as March 16, 2012.  Merely touched up to apply cleanly to latest master as of Mar 23, 2012.&lt;/p&gt;</comment>
                    <comment id="28613" author="abrooks" created="Sat, 26 May 2012 22:58:00 -0500"  >&lt;p&gt;I just ran into this issue myself. Is there anything that I could do to help get this fixed? Test writing? Patch checks? I&apos;m happy to help in any way I can.&lt;/p&gt;</comment>
                    <comment id="28614" author="jafingerhut" created="Sun, 27 May 2012 01:11:15 -0500"  >&lt;p&gt;You could examine the existing patch, including its tests, and see if it would have done what you were hoping it would do.  Add a comment here regarding whether the changes look good to you.  The attached patch is already on my weekly list of prescreened patches, but it is only one among many.&lt;/p&gt;</comment>
                    <comment id="29180" author="fogus" created="Wed, 15 Aug 2012 13:14:46 -0500"  >&lt;p&gt;The code is clean and tests test what they should test.  Regarding the questions in the test file:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;I recommend (royal) we create another ticket for the remaining clojure.set functions and discuss them there.  Once resolved the questions in the metadata.clj test file should be removed.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;tt&gt;remove&lt;/tt&gt; returns a LazySeq, but the intent of the question is clear.  I vote that remove preserve metadata as well, but that should be the topic of yet another ticket.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;One final point. I&apos;d prefer that tickets be addressed in isolation and not contain extra fixes. This is a personal preference, but one that I&apos;d like to take up on the clojure-dev list.&lt;/p&gt;</comment>
                    <comment id="29191" author="jafingerhut" created="Thu, 16 Aug 2012 00:38:41 -0500"  >&lt;p&gt;clj-916-make-into-preserve-metadata-patch1.txt dated Aug 15 2012 only changes the behavior of into so that it preserves metadata.  One or more other tickets will be created for some other functions that currently do not preserve metadata, but perhaps should.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                    <attachment id="11006" name="clj-916-make-into-and-others-preserve-metadata-patch2.txt" size="7444" author="jafingerhut" created="Fri, 23 Mar 2012 20:03:25 -0500" />
                    <attachment id="11437" name="clj-916-make-into-preserve-metadata-patch1.txt" size="3811" author="jafingerhut" created="Thu, 16 Aug 2012 00:38:41 -0500" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Approval</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10007">Ok</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Patch</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10002">Code and Test</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                        </customfields>
    </item>
</channel>
</rss>