From c41342739a3c8a0bea9d01d92dfe5ad12df4acc9 Mon Sep 17 00:00:00 2001 From: Patrick Pelissier Date: Wed, 2 Oct 2019 08:12:09 +0200 Subject: [PATCH] Reformulate --- README.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index c9141c9d..baacaabe 100644 --- a/README.md +++ b/README.md @@ -47,13 +47,11 @@ Other key designs are: * do not rewrite the C library and just wrap around it (for example don't rewrite sort but stable sort), * do not make users pay the cost of what they don't need. - -Due to the nature of the C language, 'type safe' means that a proper warning -shall be generated by the compiler in case of wrong type passed as -arguments to the functions (and not errors). You can also request -the compiler to transform all warnings into errors to get proper errors -too if you want. - +Due to the [weak](https://en.wikipedia.org/wiki/Strong_and_weak_typing#Pointers) nature of the C language for pointers, +[type safe](https://en.wikipedia.org/wiki/Type_safety) +means that at least a warning +is generated by the compiler in case of wrong type passed as +container arguments to the functions. M\*LIB should still be quite-efficient: even if the implementation may not always be state of the art, there is no overhead in using this library rather than using