Emile Cormier

If you decide to rename to `better_enums.h`, you should at least put it inside an `include` subdirectory, so that all the other files in your repository's root directory don't pollute...

For those of use willing to use C++11 features, is there a way we can write our own macro that wraps `BETTER_ENUM` and provides the necessary plumbing for a `is_better_enum::value`...

Could `extra/better-enums/n4428.h` be used for this purpose?

> You should be able to write ordinary variable-argument macros wrapping BETTER_ENUM that do any extra work that you need. Are you having difficulties with that? I haven't tried yet....

I've barked up that tree before (#135), and the author claimed concern about backward compatibility. I think compatibility with other libraries and application code should take precedence, IMHO. Another pain...

See https://gist.github.com/ecorm/8878c5075cf8557994983540a13557bc#file-main-cpp as an example of how difficult it currently is to parse an arbitrary ISO 8601 string into an arbitrary `time_point`.

Well, I think a sane way of parsing ISO 8601 _should_ be added to the C++ standard library. Other mainstream languages have an easy way to parse ISO 8601 strings....

I don't know if you've resolved your issue or not, but make sure that `USE_OS_TZDB` is the same when compiling the library separately and when compiling the application. `USE_OS_TZDB` affects...

Excellent summary, thanks! Is this library's `format` locale-indendent (that is, the overloads that don't take a `locale` object)? Or put another way, do the `format` overloads not taking a locale...

Thanks, I incorrectly assumed the standard `format` overloads not taking a `locale` were locale-independent (which is different from the _fmt_ library).