waffles@yttrx :t_blink: on Nostr: catch(…) 😎 But in all seriousness, at work we use a lot of folly, and we don’t ...
catch(…) 😎
But in all seriousness, at work we use a lot of folly, and we don’t throw exceptions. Rather we use folly optional to wrap exceptions in return codes. This is helpful in our micrososervises as we often have thrift definitions to pass option exception handling over the wire to signal failure states across services.
But at the end of the day, all of our code is little more than retry logic wrapped around a while(1) ;)
But in all seriousness, at work we use a lot of folly, and we don’t throw exceptions. Rather we use folly optional to wrap exceptions in return codes. This is helpful in our micrososervises as we often have thrift definitions to pass option exception handling over the wire to signal failure states across services.
But at the end of the day, all of our code is little more than retry logic wrapped around a while(1) ;)