Custom Query (1030 matches)

cl:last could be faster by implementing some special cases and open coding the general case.

I looked at the sbcl source for LAST, and we may have both guessed at least
partly right.

As i understand the code, they special-case both the case where N=0 and the
one where N=1, and  a  simpler iterative loop in each of those cases, and
a more generaj iterative loop for other values of N.

In addition. a compiler-macro is defined on LAST, which may expand
into one of the simpler loops if N is constant and does not call out-of-line
code in any event .

in the current trunk CCL (and likely earlier) pm x8664

? (upgraded-array-element-type '(signed-byte 60))
FIXNUM

ok. but

? (upgraded-array-element-type '(unsigned-byte 59))
(UNSIGNED-BYTE 64)

does not seem to be ok

I think that the problem is likely in the order in which CASE clauses are tested by CCL::CTYPE-SUBTYPE

example code attached.

On windows Output of the read-line call is different depending on the line endings in the file, and currently only reading files with unix style line endings begets the appropriate behavior.

A file rvs-prune.txt consisting of -d 30 -r m:\dump\ because nothing can ever be easy

with windows line endings read by the attached function produces "-d 30 -r m:
dump

with mac "ecause nothing can ever be easy

with unix (expected output) "-d 30 -r m:
dump
"