I'd like to provide some feedback on: 5068: concurrent assertions in classes This enhancement seems like a good addition to the language, however, it introduces a difficulty regarding reclamation of classes. Since concurrent assertions do not have a lifetime, a class containing concurrent assertions will likely become persistent. This may be OK for certain uses, but I wanted to point that out. Either the rules for assertion lifetime are enhanced (e.e., allow users to destroy an assertion) or else document the potential memory leak in the LRM. Arturo -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Fri Nov 28 19:03:11 2014
This archive was generated by hypermail 2.1.8 : Fri Nov 28 2014 - 19:04:09 PST