status changed; resolution set

Neil Groves — Sun, 15 Apr 2012 08:27:04 GMT

status new → closed
resolution → invalid

This report is invalid. There is not an automatic construction from string literals. Historically many versions ago, there was an attempt to handle string literals seamlessly. This proved to not work well.

Your example is an iterator_range explicitly constructed to be of length 4 ie. the null terminator has been removed from the const char* range.

When compared to the const char[5] literal "Olaf\0" this is handled as any array would be. Since the size of the array is different it is not considered equal.

When dealing with literal strings it is documented that one should use as_literal. http://www.boost.org/doc/libs/1_49_0/libs/range/doc/html/range/reference/concept_implementation/semantics/functions.html

Sun, 15 Apr 2012 08:35:23 GMT

Hi Neil,

When compared to the const char[5] literal "Olaf\0" this is handled as any array would be.

That's the core of the problem. I did not expect this string literal to be handled as an array. Wouldn't it be safer to disallow implicit conversion of arrays and require the user to use as_array or as_literal to explicitly state what conversion is desired?

Boost C++ Libraries: Ticket #6716: Unexpected behaviour when constructing iterator_range from string literal

status changed; resolution set