Oh god, more grammatic tweaks.

This commit is contained in:
Michael Bayne
2011-06-13 14:02:52 -07:00
parent de9e5217be
commit 402711b766
+4 -4
View File
@@ -29,10 +29,10 @@ certain design goals.
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. Note that the interfaces 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 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 mutable classes. Use the interfaces anyway and then profile your application
application to determine whether there are places where you need to sacrifice to determine whether there are places where you need to sacrifice code
code clarity and safety on the altar of higher performance. 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