It may be useful to annotate more things - objects, types, parameters, arguments, requests. (Hat tip to Dave Ungar's Ly :-)
objects
object {
is abstract
method x is required {}
method y is required {}
}
requests:
print (collection.at(12) is readonly)
actor.message(1,2) is oneway
parameters:
class foo(size is manifest) {
}
I think there may be an issue here between definition and use - does an annotation make something have some property method fast is optimised { .. } (like "assume") or test that something has the property (like "assert"). Or does this depend on where the annotations go?
It may be useful to annotate more things - objects, types, parameters, arguments, requests. (Hat tip to Dave Ungar's Ly :-)
objects
requests:
parameters:
I think there may be an issue here between definition and use - does an annotation make something have some property
method fast is optimised { .. }
(like "assume") or test that something has the property (like "assert"). Or does this depend on where the annotations go?