add read/write timeouts to net2
Add IsEqual and RemoveIf to container/set
Merge pull request #59 from PatrickDropbox/master

Fix set's intersect.  We shouldn't mutate the map while iterating over it.
Merge pull request #60 from PatrickDropbox/master

forgot to run go fmt.
Add tests and use safer method for RemoveIf
Merge pull request #58 from arsham-f/master

Add IsEqual and RemoveIf to container/set
Update contributor list
mock memcache client: implement Delete
mock memcache client: CAS mismatch returns StatusKeyExists, not StatusItemNotStored
Merge pull request #61 from vadimg/fixmockmemcached

Mock Memcached fixes
Update contributor list
add tests for net2 timeouts
Merge pull request #57 from vadimg/master

add read/write timeouts to net2
[sqltypes] Add support to serialize and deserialize them
Get rid of panic and use iota
Refactor repeated logic to helper method writeBinary
Merge pull request #62 from rajatgoel/master

[sqltypes] Add support to serialize and deserialize them
bugfix: race in sync2.BoundedRWLock

There's a race in the BoundedRWLock implementation which lets readers to
sneak through while a writer is holding the lock.

Example race:
 * Writer A calls `WUnlock()` and wakes up a whole bunch of readers inside
   `processQueue()` and releases `rw.control`.
 * Writer B arrives right before any of the readers could acquire the `rw.control` lock.
   Writer B thinks there are no readers and `rw.nextWriter == nil`. So it thinks it has
   an exclusive lock.
 * Finally the readers actually wake up, acquire `rw.control`, increment the `readers` counter.
   Now you've both readers and writer holding the lock at the same time.

Fix:

Whenever a reader is woken up, we also increment `rw.readers` counter immediately. This prevents
a writer from racing with the readers. Readers decrement the counter when they unlock as before.
Document the set interface
Add thread-safety comment