Some editing of the performance notes

This commit is contained in:
Michael Bayne
2011-06-13 14:01:59 -07:00
parent e79813cc0f
commit de9e5217be
+5 -5
View File
@@ -28,11 +28,11 @@ certain design goals.
example, a `Rectangle` can accept an `IRectangle` to indicate to the caller 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 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 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 that the recipient will mutate it and wreak havoc. Note that the interfaces
interfaces have performance implications in extremely performance sensitive have a very small, but non-zero performance cost versus direct use of the
situations. So use them anyway and then profile your application to determine mutable classes. So use the interfaces anyway and then profile your
whether there are places where you need to sacrifice code clarity and safety application to determine whether there are places where you need to sacrifice
to obtain higher performance. code clarity and safety on the altar of higher performance.
* The library supports garbage creation avoidance (for applications which are * The library supports garbage creation avoidance (for applications which are
sensitive to garbage collection pauses, like video games). For example, in sensitive to garbage collection pauses, like video games). For example, in