Can such use-cases be nested? E.g. : {code} Session s = ...; UseCaseStats aStats = s.markUseCase( "a" ); ... UseCaseStats bStats = s.markUseCase( "a.b" ); ... bStats.end(); aStats.end(); {code}
Or does starting a new "use-case collection" cause an implicit end of the earlier one?
I made an assumption about the API above... namely that it exists as such :) But thus far there has been no discussion of what such an API would look like, usage-wise; so far we have just discussed what to collect.
|