Nikita Kniazev

The rule should not do such a thing. Moreover, you can add a custom parser that will handle any type you want, `attr` 'parser' is in this category already.

> If it's going to be treated as an error anyway, why not show a simple message by static_assert? I would love to get a PR :-) The last time...

> I actually don't remember who/where told me about inheriting from containers and x3::variant, but IIRC it was somewhere here on a different issue. All this stuff is an effect...

> The variant example is mentioned I am sorry, but you did not mention it and said just above that the documentation should have it. > (at least at the...

Does it really has something to do with IEEE 754 compliance? Unfortunately I do not have a copy of the paper, if the paper does not allow quoting at least...

Thanks for reporting. Unfortunately, I see no potential problems on these lines ([grammar.ipp#L271](https://github.com/boostorg/spirit/blame/60c971df52ee06932c8344be5dbaecd1219a69fa/include/boost/spirit/home/classic/core/non_terminal/impl/grammar.ipp#L271), [grammar.ipp#L167](https://github.com/boostorg/spirit/blame/60c971df52ee06932c8344be5dbaecd1219a69fa/include/boost/spirit/home/classic/core/non_terminal/impl/grammar.ipp#L167)).

I understand, thanks again, let leave the issue opened as I might be investigating these warnings in the future.

1. The code contains implementation-defined behavior ([\[lex/1.1\]](https://eel.is/c++draft/lex#phases-1.1)). Please rewrite it without unicode characters in the source code. 2. Do you intentionally use `std::string` with unicode? That will encode it with...

> Yes. I would like to process the UTF-8 as plain 8-bit chars as the file format itself (say the control characters) is exclusively made up of ASCII characters, like...

Mixing unicode with non-unicode parsers, using unicode parsers on non-unicode input, or non-unicode parsers on unicode input is not supported. I had been researching the problem and prototyping a solution...