But far better, if you have any say in it, is making the callback the final argument to someFn.
someFn arg1, arg2, arg3, -> doStuffInACallback()
The thing about coffeescript is that most of the pitfalls being discussed here are very easily avoided with a modicum of experience and sense, whereas in javascript, many of the core issues simply cannot be avoided, and must be worked around in plainly ugly and bug prone ways (see: string concatenation, this/that juggling, "])})]));, just for starters).
someFn(arg1, arg2, (-> doStuffInACallback()), arg3)
But far better, if you have any say in it, is making the callback the final argument to someFn.
someFn arg1, arg2, arg3, -> doStuffInACallback()
The thing about coffeescript is that most of the pitfalls being discussed here are very easily avoided with a modicum of experience and sense, whereas in javascript, many of the core issues simply cannot be avoided, and must be worked around in plainly ugly and bug prone ways (see: string concatenation, this/that juggling, "])})]));, just for starters).