Timeline for Should I be returning promises from any function that uses them?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2018 at 17:44 | comment | added | Fabio | Async in .net is very good example, because of strong types you are forced to return Task(Promise in .net world). So one method which uses asynchronous approach and all callers should be changed to return it too. | |
| Jan 12, 2016 at 1:23 | vote | accept | TwainJ | ||
| Jan 12, 2016 at 1:23 | comment | added | TwainJ | I believe it really was the "infectiousness" of asynchrony that worried, more than Promises. I just felt I might be missing something in the proper patterns of using Promises that might mitigate that in some way. I'm now confident that that is not something I was just missing. Thanks all for helping me sort it out. | |
| Jan 9, 2016 at 12:34 | comment | added | Ixrec | +1 Pretty much exactly what I wanted to write. The only thing I'd add is that this is just as true if you use callbacks instead of promises, or have functions that "convert" a callback to a promise or vice versa, just to hammer home the point that async-ness is inherently "infectious", and it's got nothing to do with promises specifically. | |
| Jan 9, 2016 at 5:10 | comment | added | jfriend00 | @Basilevs - I added another paragraph to the end of my answer. | |
| Jan 9, 2016 at 5:09 | history | edited | jfriend00 | CC BY-SA 3.0 | added 618 characters in body |
| Jan 9, 2016 at 5:01 | comment | added | jfriend00 | @Basilevs - well, that's just the way it is with async. Any operation that uses an async API immediately changes the entire operation to be async. There's nothing you can do about that - that's just the way it is. | |
| Jan 9, 2016 at 3:39 | history | answered | jfriend00 | CC BY-SA 3.0 |