WIP: [#40] types: Generate StableMarshaler methods for refs #41
No reviewers
TrueCloudLab/storage-core-committers
TrueCloudLab/storage-core-developers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api-go#41
Loading…
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-api-go:feature/40-autogen_marsh/refs_grpc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: Airat Arifullin a.arifullin@yadro.com
@ -41,3 +33,1 @@
proto.BytesMarshal(ownerIDValField, buf, o.val)
return buf
return message.StableMarshal[*refs.OwnerID](o, buf)
@fyrchik , in this comment you said the marshaler should be replaced by the
_frostfs.pb.go
.I'm afraid we cannot do like that because types in the
refs/* (excpet for refs/grpc)
arerpc
-API specific and rather created by hand while_frostfs.pb.go
is (obviosly) auto-generated. But I think I found the tradeoff using these invocations.I would be glad to consider the good suggestion how we can deal with that
If we do it like this, these would be lots of unnecessary allocations.
I would rather remove intermediate wrappers, see https://github.com/nspcc-dev/neofs-api-go/issues/395 .
This can complicate things on the SDK side, though.
refs https://github.com/nspcc-dev/neofs-api-go/issues/395
[#40] types: Generate StableMarshaler methods for refsto WIP: [#40] types: Generate StableMarshaler methods for refsPostponed.
Pull request closed