@jaffathecake @stefanpenner The point of template string *TAGS* is to process the arguments piece-wise. If not doing that, just use a fn.
@domenic @stefanpenner @jaffathecake I think I'm just missing what you believe is the platonic essence of template literals.
-
-
@wycats@stefanpenner I keep seeing@domenic and@jaffathecake try to clarify that they're referring to _tagged_ templates... -
@justinfagnani@stefanpenner@domenic@jaffathecake if the rule is "${} has to mean something special" then "no interpolation" qualifies -
@justinfagnani@stefanpenner@domenic@jaffathecake but surely strip` foo bar${interp} baz ` is fine too -
@wycats@justinfagnani@stefanpenner@jaffathecake Why do that? It disallows strip(stringPassedAsAnArg), to save you two chars. -
@domenic@justinfagnani@stefanpenner@jaffathecake strip([arg]) works -
@domenic@justinfagnani@stefanpenner@jaffathecake also allows you to have a policy around whether to strip leading interpolated WS -
@domenic@justinfagnani@stefanpenner@jaffathecake or just literal whitespace.
End of conversation
New conversation -
-
-
@domenic@stefanpenner@jaffathecake getters are also "feel like properties, memoize if appropriate". -
@domenic@stefanpenner@jaffathecake and "I commit to continuing to make them feel like properties" -
@wycats@stefanpenner@jaffathecake Yes. And *TAGGED* template literals are "I intend to process every interpolated value piecewise." -
@wycats@stefanpenner@jaffathecake plus "This is not a normal template literal. Every time you see ${} something special is happening." -
@domenic@stefanpenner@jaffathecake "no interpolation allowed" is a valid processing and an improvement over hbs(`...`)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.