8 Commits

Author	SHA1	Message	Date
Anton Bachin	5ce9537d66	Made all-constexpr (slow) enums an opt-in feature.	2015-05-27 09:02:27 -05:00
Anton Bachin	156b9d9b04	Used explicit inline functions to simplify type hierarchy, also simplified iterables names.	2015-05-27 09:00:19 -05:00
Anton Bachin	d01aacd454	Prefixed .to_* methods with underscores to avoid name conflicts.	2015-05-27 08:47:17 -05:00
Ben Alex	832dad561f	Modifications to support aggressive compiler warning levels. ... These modifications ensure enum.h can be used in a wider selection of end user projects without triggering warnings. GCC 4.9.2 was used with the following warning flags set: -Wall -Wextra -Wshadow -Weffc++ -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-long-long -Wstrict-aliasing -Werror -pedantic -std=c++1y -Wformat=2 -Wmissing-include-dirs -Wsync-nand -Wuninitialized -Wconditionally-supported -Wconversion -Wuseless-cast -Wzero-as-null-pointer-constant This commit includes the modifications required to enable successful use of enum.h via both the "test" and "example" directories.	2015-05-27 14:18:12 +10:00
Anton Bachin	d9bd109172	Removed range properties. ... They can now be easily computed using the random access iterators. There appears to be a slight performance improvement.	2015-05-18 09:29:35 -05:00
Anton Bachin	6c60edcc46	Subscript operator for iterables and tests for constexpr iterators.	2015-05-17 22:13:44 -05:00
Anton Bachin	14bc834f7d	Made to_string conversion constexpr and removed the last of the weak symbols. ... The interface is now uniformly constexpr, including to_string and the _names iterable. Without the weak symbol, the remaining code is also entirely standard C++. The compile-time string trimming code in this commit has a negative impact on performance. The performance test is now twice as slow as including <iostream>, whereas before it was faster. That test declares an excessive number of enums, though, so perhaps in typical usage, and with some future optimizations, the impact will not be so significant. There may be other ways to solve this, such as providing a version of the macro that does not trim strings at compile time, but only checks if they need trimming. If some string does need trimming, that macro would fail a static_assert and ask the user to use the slow macro.	2015-05-17 21:29:26 -05:00
Anton Bachin	dd606fd450	Initial release.	2015-05-11 17:38:41 -04:00