15:27:56beachAnd I frankly don't see any way that something like this could be specified more loosely. As in, I can give examples like yours, but can't think of any general way of phrasing it.
15:28:10beachThat doesn't mean it can't be done, of course.
15:28:42beachAnd, people might object to any such specification, given this "gut feeling".
15:32:57Bikewhat i'm imagining is the page on aref etc say "an error might be signaled", and then elsewhere there's a section explaining where an error can be signaled, sort of like 3.5.1.1.1
15:33:08Bikeso i don't think people would care much any more than they do about 3.5.1.1.1 or "error terminology"
3:09:43moon-childso, sbcl supports ATOMIC-INCF on conses. At high safety levels, it will generate a cas loop; at low safety, it will take advantage of XADD (not checking whether the object pointed-to is actually a fixnum). Presumably the latter behaviour is not desirable for sicl. So atomic-incf
3:10:00moon-childshould support only standard object slots which have type fixnum