Re: TODO list for Guile R7RS support

[Alex Shinn]

On Thu, Feb 23, 2012 at 7:06 AM, Andy Wingo <address@hidden> wrote:
>
>> * datum labels for circular and shared substructures
>
> Yes!

Note this is one thing a reference implementation will
be provided for.

>> * nan? and finite? now accept complex numbers
>>   (should probably change inf? and infinite? as well)
>
> Do you need to file a bug with the spec?  Have you?

A complex number is nan? if either component is nan.
A complex number is finite? if both components are finite.

Implementations may not necessarily support complex
numbers with nan or inf components.

>> * R7RS exceptions
>
> Are they like R6RS exceptions?

Yes, just the exceptions with no condition hierarchy.

> The semantics of the interaction of guard with dynamic wind is still
> batshit crazy, and I hope guard doesn't make it into the spec as is.

Not disagreeing, but you'll need to clarify what about it
is crazy and ideally provide an alternative :)

>> * define-library
>
> A big one, and something to check in the newer specs..

It hasn't change much and shouldn't be too hard.

>> * vector->string and string->vector
>
> Real wtf procedures, if you ask me...

Agreed.

>> * write bytevectors with #u8 (and elements in hex) by default?
>
> Is this incompatible wrt srfi-4?

R7RS says nothing about the base.  So long as you write with
a prefix, e.g. #u8(#xFF ...) this is compatible with SRFI-4.

>> * make sure {map,vector-map,string-map} are multi-return safe
>
> This is an interesting one.  It would be nice to have expandable stacks
> so we can do the straightforward implementation.  Dunno.

The straightforward implementation doesn't need expandable
stacks.  Basically, all you need to do is avoid mutation - i.e.
cons up a list and reverse at the end.

We will also provide a reference implementation of this.

-- 
Alex