As far as I (Will) understand it, this is an error in the current implementation, unless it makes sense for a set-cons to have a non-set tail.
Maybe I don't fully understand this issue. Raffi, does it make sense for set-cons to have a non-set tail, in the same way that cons can take a non-list as its second argument? Or must a set-cons have an honest-to-goodness set as its tail?
In the latter case, I think we should enforce the set-ness of the tail.
From a discussion between Will and Raffi:
Will's question:
Raffi responded in the affirmative, with this example:
As far as I (Will) understand it, this is an error in the current implementation, unless it makes sense for a set-cons to have a non-set tail.
Maybe I don't fully understand this issue. Raffi, does it make sense for set-cons to have a non-set tail, in the same way that cons can take a non-list as its second argument? Or must a set-cons have an honest-to-goodness set as its tail?
In the latter case, I think we should enforce the set-ness of the tail.
Thanks!