summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYury Selivanov <yury@magic.io>2018-04-02 15:13:27 -0400
committerYury Selivanov <yury@magic.io>2018-04-02 15:13:58 -0400
commit657f076cb92e98bda97faf493c04fc9c47869d30 (patch)
tree73d2c4f4f33323e3bd2f808fca1450ee659bea5f
parentd566904b7cca8ec14128ab2941a6edac34e06371 (diff)
downloadimmutables-657f076cb92e98bda97faf493c04fc9c47869d30.tar.gz
immutables-657f076cb92e98bda97faf493c04fc9c47869d30.zip
readme: Update benchmarks link; fix typo
-rw-r--r--README.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.rst b/README.rst
index 40368fb..72aaf21 100644
--- a/README.rst
+++ b/README.rst
@@ -21,7 +21,7 @@ essentially O(1) for relatively small mappings.
Below is a visualization of a simple get/set benchmark comparing
HAMT to an immutable mapping implemented with a Python dict
copy-on-write approach (the benchmark code is available
-`here <https://gist.github.com/1st1/9004813d5576c96529527d44c5457dcd>`_):
+`here <https://gist.github.com/1st1/292e3f0bbe43bd65ff3256f80aa2637d>`_):
.. image:: bench.png
@@ -40,7 +40,7 @@ immutables.Map
The ``Map`` object implements ``collections.abc.Mapping`` ABC
so working with it is very similar to working with Python dicts.
-The only exception is its ``Map.set()`` and ``Map.delete()`` methods
+The only exception are its ``Map.set()`` and ``Map.delete()`` methods
which return a new instance of ``Map``:
.. code-block:: python