Grr, Markdown doesn't do the right thing with multi-paragraph line items.
This commit is contained in:
@@ -28,12 +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.
|
that the recipient will mutate it and wreak havoc. Bear in mind that the
|
||||||
|
interfaces have performance implications in extremely performance sensitive
|
||||||
Bear in mind that the interfaces have performance implications in extremely
|
situations. So use them anyway and then profile your application to determine
|
||||||
performance sensitive situations. So use them 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 to obtain 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
|
||||||
|
|||||||
Reference in New Issue
Block a user