Custom Query (1630 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (55 - 57 of 1630)

Ticket Resolution Summary Owner Reporter
#1737 fixed srfi-41: missing dependency on srfi-1 Kon Lovett Mario Domenech Goulart
Description

See http://salmonella-linux-x86.call-cc.org/master-debugbuild/gcc/linux/x86/2021/03/28/salmonella-report/install/srfi-41.html

#1736 fixed Incomplete SRFI-46/R7RS tail pattern support Vasilij Schneidermann
Description

I've run into an expansion error when trying to install (chibi optional). It's using a tail pattern of the (binding ... . rest) kind. SRFI-46 only shows one tail pattern example of the ((binding ...) . rest) kind, but R7RS is explicit about allowing both:

⟨transformer spec⟩ −→
(syntax-rules (⟨identifier⟩*) ⟨syntax rule⟩*)
| (syntax-rules ⟨identifier⟩ (⟨identifier⟩*)
⟨syntax rule⟩*)
⟨syntax rule⟩ −→ (⟨pattern⟩ ⟨template⟩)
⟨pattern⟩ −→ ⟨pattern identifier⟩
| ⟨underscore⟩
| (⟨pattern⟩*)
| (⟨pattern⟩+ . ⟨pattern⟩)
| (⟨pattern⟩* ⟨pattern⟩ ⟨ellipsis⟩ ⟨pattern⟩*)
| (⟨pattern⟩* ⟨pattern⟩ ⟨ellipsis⟩ ⟨pattern⟩*
. ⟨pattern⟩)
| #(⟨pattern⟩*)
| #(⟨pattern⟩* ⟨pattern⟩ ⟨ellipsis⟩ ⟨pattern⟩*)
| ⟨pattern datum⟩

According to SRFI-46 alexpander does support both patterns just fine, the error message originates from synrules.scm. I've attached a file with simplified examples for both the working and not working pattern. I've also done a brief check across R7RS-compliant Scheme implementations, it seems that Cyclone doesn't support it either, while Chibi, Kawa, Gauche, Sagittarius and Foment do.

#1734 fixed r7rs bytevector syntax incorrectly reads second passed expression as bytevector body Diego
Description

On (import r7rs), something like #f32(1.0 2.0) doesn't work - the syntax instead ignores the first passed expression, and uses the second expression as the vector body. So you have to do something pretty weird like #f32()(1.0 2.0) for this to work.

Indeed, read-srfi-4-vector in the file r7rs.scm seems to have an extra call to read. The attached (completely trivial) patch should fix this.

Note: See TracQuery for help on using queries.