Does anyone else have a use case for multi-shot co...
# coroutines
Does anyone else have a use case for multi-shot continuations?
Can you describe your use case?
is somewhat like that. Or, for non async type code, look at 'sequence's
☝️ 1
This is a very misleading paper. You don’t actually need coroutines for back-propagation and if you actually implement it like they claim in the paper the code with coroutines is not simpler, but much slower than without coroutines.
Attempting to replicate their paper actually led me to writing this very simple back-propagation engine without any coroutines at all:
🔥 1
The only reason I wish I formally studied development is I am sure I know what’s being discussed here, but I would call it “The thingy does the thingy with the thingy”
Anyone got a good resource on continuations? Ideally Kotlin but any language works.
The coroutines KEEP might be what you’re looking for
Hello! Is there any way to make coroutine stack trace more informative?
@elizarov I saw your implementation, but it only supports first-order derivatives...
What are you doing that needs higher-order derivatives?
I'm not doing anything, but it's not that difficult to implement symbolically (cf. I don't think CPS is necessary to implement reverse mode AD, but I suspect multi-shot continuations would simplify the implementation, and in any case would be a neat demonstration of the language feature
I also saw your implementation of multi-shot continuations, maybe that can be adapted to something less generic which does not require reflection
Symbolically? What’s the use-case?
Our implementation uses symbolic differentiation, so higher order is just an extra case statement. There are applications (e.g. Newton's method, conjugate gradient, etc.) but the real motivation is just because we can and for the sake of completeness