From 83f5839e2c1fa0c3c2c579c63eb52351a757d9cc Mon Sep 17 00:00:00 2001 From: narimiran Date: Tue, 19 Feb 2019 09:07:25 +0100 Subject: [PATCH] manual: fix broken sentence --- doc/sets_fragment.txt | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/sets_fragment.txt b/doc/sets_fragment.txt index 5a996e550..7e53f15f1 100644 --- a/doc/sets_fragment.txt +++ b/doc/sets_fragment.txt @@ -1,18 +1,17 @@ The set type models the mathematical notion of a set. The set's basetype can only be an ordinal type of a certain size, namely: - * ``int8``-``int16`` - * ``uint8``/``byte``-``uint16`` - * ``char`` - * ``enum`` +* ``int8``-``int16`` +* ``uint8``/``byte``-``uint16`` +* ``char`` +* ``enum`` -For signed integers the set's base type is defined to be in the +or equivalent. For signed integers the set's base type is defined to be in the range ``0 .. MaxSetElements-1`` where ``MaxSetElements`` is currently always 2^16. -or equivalent. The reason is that sets are implemented as high -performance bit vectors. Attempting to declare a set with a larger type will -result in an error: +The reason is that sets are implemented as high performance bit vectors. +Attempting to declare a set with a larger type will result in an error: .. code-block:: nim