PROPOSAL: & and && operators about _hyperscript

[1cg]

I wonder if we should drop && and just go w/ what hypertalk did

[benpate]

The trouble here is that && is so common to most modern developers that its second nature to use. You'll have tons of cleanup to do even in the hyperscript examples.

But, I can't imagine anyone is already using && with strings, so it seems like it should be safe to overload this operator.

[dz4k]

People definitely use && with strings.

if (options.prefix && options.selector) {
  // check the existence of prefix and selector, which are both strings
}

[benpate]

That's a fantastic example, @dz4k. It would require a small change to make your code above work correctly. If we adopted this syntax for string concatenation, you'd have to say if options.prefix and options.selector then... instead.

I think this is a cool idea, but it would only work if we're okay with removing (or confusing) support for the javascript && operator. I'll leave that decision for the big boss, but my first thought is that it may not be worth the confusion.

[dz4k]

http://rigaux.org/language-study/syntax-across-languages.html#StrngStrnCnct

AFAIK ^ isn't used for anything as of now.

P.S. Is this really necessary when template literals exist?

[benpate]

True. It's probably more trouble than it's worth. Let's just close it :)