From de9e5217be2c680c71fb4bfe65ffb820d815d4d9 Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Mon, 13 Jun 2011 14:01:59 -0700 Subject: [PATCH] Some editing of the performance notes --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 24b9bbb..5b88fc1 100644 --- a/README.md +++ b/README.md @@ -28,11 +28,11 @@ certain design goals. example, a `Rectangle` can accept an `IRectangle` to indicate to the caller that it will not (and indeed cannot) mutate the supplied entity. Similarly, a read-only interface can be returned to a private internal field without fear - that the recipient will mutate it and wreak havoc. Bear in mind that the - interfaces have performance implications in extremely performance sensitive - situations. So use them anyway and then profile your application to determine - whether there are places where you need to sacrifice code clarity and safety - to obtain higher performance. + that the recipient will mutate it and wreak havoc. Note that the interfaces + have a very small, but non-zero performance cost versus direct use of the + mutable classes. So use the interfaces anyway and then profile your + application to determine whether there are places where you need to sacrifice + code clarity and safety on the altar of higher performance. * The library supports garbage creation avoidance (for applications which are sensitive to garbage collection pauses, like video games). For example, in