http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJ-767 Clojure <p>Per <a href="http://groups.google.com/group/clojure-dev/browse_thread/thread/2191cbf0048d8ca6">Rich's comment</a>:</p> <blockquote><p>Shift ops would be limited to primitives only. Default versions 64-bit, but explicit shift-int versions for 32 bits.</p></blockquote> CLJ-767

Remove support for non-primitive bit-shift operations

Enhancement Minor Closed Declined Unassigned Alexander Taggart Mon, 4 Apr 2011 00:10:58 -0500 Wed, 25 May 2011 12:12:21 -0500 Wed, 25 May 2011 12:12:19 -0500 0 1 <p>Rather than changing the behaviour of the extant unchecked ops (see the original discussion), I've created three new namespaces:</p> <ul> <li><tt>clojure.unchecked</tt>: Contains unchecked versions of the primitive cast functions. Removed the <tt>unchecked-</tt><em>prim</em> cast functions that were added to core recently.</li> <li><tt>clojure.unchecked.long</tt>: Contains unchecked, long-arg versions of the numeric and bit-op functions from core.</li> <li><tt>clojure.unchecked.double</tt>: Contains unchecked, double-arg versions of the numeric functions from core.</li> </ul> <p>Note that the <tt>clojure.unchecked</tt> namespace idea was first proffered by Rich in the comments on <a href="http://dev.clojure.org/jira/browse/CLJ-441" title="Add unchecked coercions"><del>CLJ-441</del></a>.</p> <p>This does way too much, and thus makes it hard to talk about.</p> <p>Moving unchecked coercions into unchecked ns is ok, and would make a fine and acceptably-sized patch.</p> <p>unchecked double makes no sense to me at all - no double ops are checked</p> <p>There seems to be general confusion about unchecked vs primitive-taking. Only a small subset of ops have the overflow checking that is turned off by 'unchecked'</p> <p>There's no sense in which the interacts with &#42;unchecked-math&#42;, nor with the latest numerics approach (primitive semantics by default)</p> <p>There's a ton of duplication with things already in Numbers that handle primitive overloads. esp. in combination with different primitives and objects.</p> <p>The things we need for bit ops are lost in the noise.</p> <p>What I want for bit ops is the same thing we currently (in latest) have for other ops - primitive semantics by default, no conditionals, direct mapping to JVM primitive ops.</p> <p>And separate tickets and patches for each step, please. This is simply too much to consider.</p> <p>Thanks,</p> <p>Rich</p> <p>Patch removes support for non-primitive args to bit-shift operations.</p> <p>Was effectively replaced by <a href="http://dev.clojure.org/jira/browse/CLJ-772" title="bit ops to have primitive semantics by default, no conditionals, direct mapping to JVM primitive ops"><del>CLJ-772</del></a>.</p> Global Rank