Custom Query (1030 matches)
Results (316 - 318 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1282 | fixed | sertting a large number of macro characters doen't scale well | ||
| Description |
People have reported that it can be prohibitively slow to call SET-MACRO-CHARACTER on all potential Unicode characters. I'm not surprised by this, but I'm not sure that there's a good reason to make it impractical for someone who wants to do this to do so, either. changing the data structures that CCL uses to associate characters with functions can affect things like SET-SYNTAX-FROM-CHAR and COPY-READTABLE as well as SET-MACRO-CHARACTER and (poossibly) SET-DISPATCH-MACRO-CHARACTER. |
|||
| #1340 | fixed | apparent bug in UPGRADED-ARRAY-ELEMENT-TYPE | ||
| Description |
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 |
|||
| #1351 | fixed | arm kernel does not need to be linked specially | ||
| Description |
it once did, for reasons having to do with how subprimitives were called. see <https://lists.clozure.com/pipermail/openmcl-devel/2016-February/011196.html> |
|||
