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
When using sbe-tools to generate java code, the encoders and decoders implement toString() that returns a human-readable representation of all the fields of the message. For example:
Having a human-readable representation makes debugging much, much easier, as you can print the SBE messages and check what exactly you're sending/receiving.
When generating rust, currently there's nothing like the java's toString(). The encoders and decoders derive Debug, but it prints just the name of the struct and the buffer, which is not that useful.
Could we implement Display using the exactly same format as Java for both encoders and decoders?
The text was updated successfully, but these errors were encountered:
When using sbe-tools to generate java code, the encoders and decoders implement
toString()
that returns a human-readable representation of all the fields of the message. For example:Having a human-readable representation makes debugging much, much easier, as you can print the SBE messages and check what exactly you're sending/receiving.
When generating rust, currently there's nothing like the java's
toString()
. The encoders and decoders deriveDebug
, but it prints just the name of the struct and the buffer, which is not that useful.Could we implement
Display
using the exactly same format as Java for both encoders and decoders?The text was updated successfully, but these errors were encountered: