> We need to get a new keyword for defining such a variable, I think > "transaction" is too long, we could use "safe" for this reason. The proposal looks good. But isn't this more a language issue at this point? Seems like we'll have to figure out the behavior we want first. Also, "safe" is way too general and can be confused with tainting and other data guarding methods. Since it's a transaction, why not "trans"? -Nate
- RFC 130 (v1) Transaction-enabled variables for Perl6 Perl6 RFC Librarian
- Re: RFC 130 (v1) Transaction-enabled variables fo... Nathan Wiger
- Re: RFC 130 (v1) Transaction-enabled variables fo... Chaim Frenkel
- Re: RFC 130 (v1) Transaction-enabled variables fo... David L. Nicol
- Re: RFC 130 (v1) Transaction-enabled variable... Chaim Frenkel