Adding Go's Defer to the TypeScript Compiler

geostyx 34 minutes ago |

I built a library to do something similar: https://www.npmjs.com/package/yaplib

defer is the thing I miss the most coming from Go

Article describes try/finally as a hack to get the effect of defer, but it looks to me like it's the other way around? Try/finally is more traditional, in one form or another.

Rohansi 3 hours ago | |

It's also necessary here because TypeScript has exceptions and you'd expect your `defer`s to execute even when an exception is thrown.

kaashif 3 hours ago | |

If the idea of computers is that they remember stuff for you and do stuff for you, then both try/finally and defer seem like hacks to work around not having RAII like e.g. Rust or C++ where resources are closed/disposed of/deallocated automatically.

Try X finally dispose of all resources. X, defer clean up X. Or how about just X and cleanup is done automatically, with the author of the resources deciding what is needed to clean X up.

mcintyre1994 3 hours ago | | |

JS has the using keyword for this: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

kaashif 2 hours ago | | |

What if you forget to use that and just use let or const? It is better than plain try-finally or defer because you don't have to remember how to dispose of the resources but in terms of remember to dispose of the resource at all, I don't think that is all that different from Python's with or Java's try-with-resources. You can just forget to use using, with, try-with-resources.

There isn't any way to forget to drop a resource if you have RAII.

throw-the-towel 6 minutes ago | | |

Yes, but you also have this problem with `defer`.

okigan 42 minutes ago | | |

it's mesmerizing that the fantastic ergonomics of RAII have not propagated to other languages.

It's way easier to use, much clear, less typing, more predictable runtime behavior.

RAII... terrible name, great concept!

fg137 1 hour ago |

Would call stack/source map reasonably work with this?