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
Whilst iterating over the official goproto repo, many developers asked for reasons for which code generation fast paths (specifically related to marshalling/unmarshalling) implementation were never done. One of the answers given by the owners was that the big code size was a problem for some environments.
Might this something we need to consider in the scope of the cosmos ecosystem?
A solution could be generating a build tag for slow paths, ex:
types.slow.pb.go
// +build slow...reflectioncode...
types.pb.go
// +build !slow
.. fastpathcode ...
The text was updated successfully, but these errors were encountered:
Whilst iterating over the official goproto repo, many developers asked for reasons for which code generation fast paths (specifically related to marshalling/unmarshalling) implementation were never done. One of the answers given by the owners was that the big code size was a problem for some environments.
Might this something we need to consider in the scope of the cosmos ecosystem?
A solution could be generating a build tag for slow paths, ex:
types.slow.pb.go
types.pb.go
The text was updated successfully, but these errors were encountered: