Revision: 7680
Author: [email protected]
Date: Fri Mar 5 10:29:47 2010
Log: Edited wiki page through web user interface.
http://code.google.com/p/google-web-toolkit/source/detail?r=7680
Modified:
/wiki/LightweightCollections.wiki
=======================================
--- /wiki/LightweightCollections.wiki Fri Mar 5 10:28:09 2010
+++ /wiki/LightweightCollections.wiki Fri Mar 5 10:29:47 2010
@@ -34,7 +34,7 @@
We begin by acknowledging that the design of anything as fundamental as
collection types is bound to be contentious, so the plan is to start small
and establish some patterns for simple, high-value collections: `Array` and
`Map`.
=== Principles ===
-_Assertions, not exceptions._ Assertions, when turned off, can be compiled
away. Code written to defensively check for and throw exceptions is very
hard to optimize. Hosted mode always has assertions on, so any well-tested
code ought to execute assertions during normal testing.
+_Assertions, not exceptions._ Assertions, when turned off, can be compiled
away. Code written to defensively check for and throw exceptions is very
hard to optimize. Development mode (was hosted mode) always has assertions
on, so any well-tested code ought to execute assertions during normal
testing.
_Types and methods must be used properly to perform properly._ Lightweight
collections are in no way defensive. Improper use generates an assertion
failure or, if assertions are disabled, undefined behavior. The corollary
is that the API can be designed for maximum efficiency.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
