You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially, hybrid.Lambda was made to bind hybrid.Lambda instance as self in next/error/init calls. That allowed runnable implementations via hybrid.Lambda to have access to a persistent state (like any other runnable does).
However, the most common hybrid.Lambda usage pattern these days is actually a stateless runnable.
So, to simplify the common use case, we're making hybrid.Lambda stateless (no reference to self), and we're introducing hybrid.StatefulLambda that'll behave like hybrid.Lambda did so far.
Initially,
hybrid.Lambda
was made to bindhybrid.Lambda
instance asself
innext
/error
/init
calls. That allowed runnable implementations viahybrid.Lambda
to have access to a persistent state (like any other runnable does).However, the most common
hybrid.Lambda
usage pattern these days is actually a stateless runnable.So, to simplify the common use case, we're making
hybrid.Lambda
stateless (no reference toself
), and we're introducinghybrid.StatefulLambda
that'll behave likehybrid.Lambda
did so far.Going forward, the expected usage is:
The text was updated successfully, but these errors were encountered: