Fix one more place where we were expecting lcons() to be nondestructive
to the original List; per report from Sebastian BÎck. I think this is the last such bug --- I examined every lcons() call in the backend and the rest seem OK --- but it's nervous-making that we're still finding 'em so many months after the List rewrite went in.
Showing
Please register or sign in to comment