<!-- 
RSS generated by JIRA (4.4#649-r158309) at Mon May 20 14:51:33 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/si/jira.issueviews:issue-xml/CLJ-1110/CLJ-1110.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Clojure JIRA</title>
    <link>http://dev.clojure.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>4.4</version>
        <build-number>649</build-number>
        <build-date>25-07-2011</build-date>
    </build-info>

<item>
            <title>[CLJ-1110] let-&gt; needs improvement</title>
                <link>http://dev.clojure.org/jira/browse/CLJ-1110</link>
                <project id="10010" key="CLJ">Clojure</project>
                        <description>&lt;p&gt;The function clojure.core/let-&amp;gt; is suboptimal in a few regards:&lt;br/&gt;
  1. It&apos;s name lends you to believe it is &quot;let-like&quot;, but it is not - it does not take a binding form, and its arguments are &apos;backwards&apos;&lt;br/&gt;
  2. It&apos;s docstring doesn&apos;t make clear that it is intended for use solely in a threading-macro expression&lt;br/&gt;
  3. It arbitrarily does not support destructuring, where it easily could.&lt;/p&gt;

&lt;p&gt;Possible solutions:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;rename it (e.g. to &quot;bind-&amp;gt;&quot;) to make clear it is not let-like&lt;/li&gt;
	&lt;li&gt;allow destructuring of the &apos;name&apos; parameter&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Google groups discussion: &lt;a href=&quot;https://groups.google.com/d/topic/clojure/67JQ7xSUOM4/discussion&quot;&gt;https://groups.google.com/d/topic/clojure/67JQ7xSUOM4/discussion&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="15839">CLJ-1110</key>
            <summary>let-&gt; needs improvement</summary>
                <type id="4" iconUrl="http://dev.clojure.org/jira/images/icons/improvement.gif">Enhancement</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="alexnixon">Alex Nixon</reporter>
                        <labels>
                    </labels>
                <created>Tue, 20 Nov 2012 09:08:00 -0600</created>
                <updated>Tue, 11 Dec 2012 01:03:39 -0600</updated>
                    <resolved>Thu, 29 Nov 2012 08:08:45 -0600</resolved>
                            <version>Release 1.5</version>
                                                        <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="30210" author="yongqli" created="Tue, 11 Dec 2012 00:22:11 -0600"  >&lt;p&gt;Has it been decided whether as-&amp;gt; supports de-structuring or not? Right now it is inconsistent.&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;(as-&amp;gt; [0 1]
      [a b]
  [(inc a) (inc b)])

 =&amp;gt; [1 2]



(as-&amp;gt; {:a 0 :b 1}
      {:keys [a b]}
  {:a (inc a) :b (inc b)})

 =&amp;gt; {:keys [1 2]}&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                    <comment id="30211" author="yongqli" created="Tue, 11 Dec 2012 00:50:08 -0600"  >&lt;p&gt;Also, what about changing the name to &lt;del&gt;&amp;gt;as? -&amp;gt;as reads like &quot;pipeline as name&quot;, whereas as&lt;/del&gt;&amp;gt; implies that you are starting a new pipeline.&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;(-&amp;gt; 0
  (-&amp;gt;as name 
    (...))&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Makes it clearer that you are consuming a pipeline and the expressions within -&amp;gt;as are no longer being influenced by -&amp;gt;.&lt;/p&gt;</comment>
                    <comment id="30212" author="yongqli" created="Tue, 11 Dec 2012 01:03:39 -0600"  >&lt;p&gt;Has the addition of -&amp;gt;&amp;gt;as been considered? That way you can use it inside a -&amp;gt;&amp;gt; like this:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;(-&amp;gt;&amp;gt; a 
  (-&amp;gt;&amp;gt;as name
    (...)))

(-&amp;gt; a 
  (-&amp;gt;as name
    (...)))&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The signature would be &lt;span class=&quot;error&quot;&gt;&amp;#91;name forms init-expr&amp;#93;&lt;/span&gt;.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Approval</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10008">Not Approved</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>