Re: maybe-commit fails unconditionally
Taylor R Campbell <[email protected]> Sat, 24 Oct 2009 15:31:44 -0400
| Newsgroups | gmane.lisp.scheme.scheme48 |
|---|---|
| Message-ID | <[email protected]> |
Date: Sat, 24 Oct 2009 14:08:39 -0400 From: Roderic Morris <[email protected]> I'm curious though, what's the reason for having maybe-commit set the proposal to #f instead of installing an empty one? After a transaction is committed, what is the value of immediately starting a new one? Unless there is a good reason to do so, installing an empty proposal would mask program errors -- and if you have a good reason to do so, then you should probably be starting a transaction explicitly anyway.