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
I'm not sure if Nevalang will have panics but if it will then we definitely need recover.
Anyway in Go recover only catches panics from same go-routine, any child go-routine must have its own deferred recover. This is not what I want usually.
Figure out why Go creators did this that way - google, ask chatGPT
Make sure its safe to implement recover this way
Think again if we could avoid panics at all
By "this way" I mean, to make things clear, empowering recovers so they can catch everything that happens in child FBP components at any level
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm not sure if Nevalang will have panics but if it will then we definitely need
recover
.Anyway in Go recover only catches panics from same go-routine, any child go-routine must have its own
defer
red recover. This is not what I want usually.By "this way" I mean, to make things clear, empowering recovers so they can catch everything that happens in child FBP components at any level
Beta Was this translation helpful? Give feedback.
All reactions