ocdtrekkie changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things Sandstorm and Cap'n Proto. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Channel logs available at https://libera.irclog.whitequark.org/sandstorm | Note that many community members are on #sandstorm:libera.chat on Matrix, and the bridge is currently disabled.
sj_ has quit [Quit: Client closed]
larjona has quit [Quit: No Ping reply in 180 seconds.]
larjona has joined #sandstorm
sj_ has joined #sandstorm
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #sandstorm
tian2992 has joined #sandstorm
sj_ has quit [Quit: Client closed]
sj_ has joined #sandstorm
<calmclam> Hi all, I'm wondering what the best practice is for error handling in cap'n proto RPC. When should you use protocol-level errors which are not explicitly defined in the IDL vs. having concrete error codes as return values in the IDL? It feels to me like error codes in the IDL are kind of discouraged, especially if you want to use pipelining. But, it seems unsatisfying to me not having the errors documented as part of the contract in the IDL.
<calmclam> s/IDL/Schema/
sj_ has quit [Quit: Client closed]
tian_ has joined #sandstorm
tian2992 has quit [Ping timeout: 252 seconds]
mnutt_ has joined #sandstorm
mnutt has quit [Ping timeout: 252 seconds]
sj_ has joined #sandstorm
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #sandstorm
sj_ has quit [Quit: Client closed]
TC01 has quit [Ping timeout: 252 seconds]
TC01 has joined #sandstorm