diff options
| author | Tyge Løvset <[email protected]> | 2021-02-02 22:50:58 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-02-02 22:50:58 +0100 |
| commit | 0f30fc925da0c3dad82990c454fb3affd02cf1b1 (patch) | |
| tree | b24d01859a6f83a109659f2b3e2cce93d42db097 | |
| parent | 831a951ab8efc969e843e71fb0ca73650c3bba4e (diff) | |
| download | STC-modified-0f30fc925da0c3dad82990c454fb3affd02cf1b1.tar.gz STC-modified-0f30fc925da0c3dad82990c454fb3affd02cf1b1.zip | |
Update README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -117,7 +117,7 @@ Outputs Highlights
----------
- **User Friendly** - Easy to use, as can be seen from the examples above. The ***using_***-declaration instantiates the container type to use. You may pass *optional* arguments for customization of value- *comparison*, *destruction*, *cloning*, *convertion types*, and more. Most methods have similar named corresponding methods in STL.
-- **High Performance** - The containers are written with efficiency, low memory usage, and small code size in mind. Most containers perform similarly to the c++ STL containers, however **cmap** and **cset** are roughly *5* times faster than the STL equivalents, *std::unordered_map* and *std::unordered_set*. See *Performance*. Also **cdeq** are in some cases significantly faster than *std::deque*, however implementations vary between different c++ compilers.
+- **High Performance** - The containers are written with efficiency, low memory usage, and small code size in mind. Most containers perform similarly to the c++ STL containers, however **cmap** and **cset** are roughly ***5 times faster than the STL equivalents***, *std::unordered_map* and *std::unordered_set*. **csmap** and **csset** are in general faster than *std::unordered_map/set* See *Performance*. Also **cdeq** are in some cases significantly faster than *std::deque*, however implementations vary between different c++ compilers.
- **Type Safe** - No more error prone casting of container types and elements back and forth from your containers. Less obscure bugs in your code. The compiler will let you know when retrieving or passing wrong container or element types to the methods.
- **Uniform API** - Methods to ***construct***, ***initialize***, ***iterate*** and ***destruct*** are intuitive and uniform across the various containers.
- **Small Footprint** - Generated executables are small, partly due to the small library code base. The example above with six different containers, compiles to an executable of *18 kb in size*, compiled with TinyC.
|