This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.

Source for ticket #129

cc

changetime

2011-05-19 15:44:00

component

WG1 - Core

description

Why not have "no value" instead of "unspecified one" in mutations procedures (set!, set-car!, set-cdr!, vector-set!, vector-fill!)

  By convention, the value returned by a mutation procedure is unspecified.

to

  By convention, mutation procedures return no value.

PS: is there any implementation returning the value being stored ?

id

keywords

milestone

owner

alexshinn

priority

major

reporter

medernac

resolution

duplicate

severity

status

closed

summary

About value returned by mutation procedures

time

2011-01-12 15:45:18

type

defect

Changes

Change at time 2011-05-19 15:44:00

author

alexshinn

field

comment

newvalue

Duplicate of #68.

oldvalue

raw-time

1305794640000000

ticket

time

2011-05-19 15:44:00

Change at time 2011-05-19 15:44:00

author

alexshinn

field

resolution

newvalue

duplicate

oldvalue

raw-time

1305794640000000

ticket

time

2011-05-19 15:44:00

Change at time 2011-05-19 15:44:00

author

alexshinn

field

status

newvalue

closed

oldvalue

new

raw-time

1305794640000000

ticket

time

2011-05-19 15:44:00

Change at time 2011-01-13 15:44:20

author

medernac

field

comment

newvalue

 Thanks for bringing this to mind about MIT-Scheme, as at least one implementation returns a value it is indeed not wise to push such a change (at least for 'set!').

oldvalue

raw-time

1294904660000000

ticket

time

2011-01-13 15:44:20

Change at time 2011-01-13 01:30:57

author

aag

field

comment

newvalue

In MIT Scheme, set! returns the previous value of the variable.

oldvalue

raw-time

1294853457000000

ticket

time

2011-01-13 01:30:57