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
We are using tuples for everything in our application for performance and compactness. I'd love to be able to replace the 200 or so //msgp:tuple directives with a single flag to the generator //go:generate msgp -tuple.
I suppose this means there'd need to be a new directive //msgp:map, orthogonal to //msgp:tuple in the default mode.
Happy to have a stab at this if you think it'd be worth including. It'd certainly make my life a lot easier!
The text was updated successfully, but these errors were encountered:
Greenpack goes a lot further than I need though. I can't trivially switch from msgp to something so different at this point in my project's life. How hard would it be to integrate those features from greenpack back into msgp?
greenpack -omit-clue gives you straight msgpack, no change in field names. But if you are doing greenpack -alltuple then there are no fieldnames to begin with, so I'm not sure what you think is different. Feel free to open an issue there with any questions, I don't want to get too off topic here.
We are using tuples for everything in our application for performance and compactness. I'd love to be able to replace the 200 or so
//msgp:tuple
directives with a single flag to the generator//go:generate msgp -tuple
.I suppose this means there'd need to be a new directive
//msgp:map
, orthogonal to//msgp:tuple
in the default mode.Happy to have a stab at this if you think it'd be worth including. It'd certainly make my life a lot easier!
The text was updated successfully, but these errors were encountered: