Conformance to the `ExpressibleByStringLiteral` makes it possible to create dangerous situation about swift-nonempty HOT 1 CLOSED

@letko-dmitry This is working as intended and holds true for ExpressibleByArrayLiteral, where we have this explicit precondition:

We consider this kind of assignment to be a programmer error, since literals are only ever added by programmers working on the project.

That said, we'd be open to introducing more explicit preconditions in the string initializers that better describe the problem, as they exist in the array literal conformance above.

We'd also be open to exploring how macros may solve for this at compile-time, e.g.:

#nonEmpty("")
          ┬─ 
          ╰ 🛑 Cannot use empty literal with '#nonEmpty'

Because we don't consider this a bug in the library, I'm going to convert it to a discussion.

from swift-nonempty.