@oxnrtr I'm pretty sure we just disagree on whether macro invocations should be required to be syntactically distinguished.
-
-
@pcwalton I'd say the current approach makes things harder to read, because ! just doesn't convey any useful information anymore. -
@oxnrtr I still disagree :) But I think Twitter is a bad medium for this. - 1 more reply
New conversation -
-
-
@pcwalton@oxnrtr type-safe printf https://www.youtube.com/watch?v=fVBck2Zngjo … awesome demo, short too. :) -
@bitemyapp@pcwalton Yes, it works perfectly well without the "OMG, all people stand back! Expect magic semantics while calling print!" - 4 more replies
New conversation -
-
-
@pcwalton Yes. "!" is fine if you are embedding a custom DSL or a different language. For most macros, that's just not the case.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@pcwalton "Is this method moving a few runtime-time checks to compile-time or is it translating embedded SQL to database calls?" ...Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@pcwalton ... those use-cases would benefit from having a clear visual distinction. Using ! for both doesn't add clarity here, just noise.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.