receiver name should not be an underscore, omit the name if it is unused
51 return slice.SetUint64(commIds)
52}
53
54func (_ *Service) attesterSubnetIndices(currentSlot primitives.Slot) []uint64 {55 endEpoch := slots.ToEpoch(currentSlot) + 1
56 endSlot := params.BeaconConfig().SlotsPerEpoch.Mul(uint64(endEpoch))
57 var commIds []uint64receiver name should not be an underscore, omit the name if it is unused
41 return cache.SubnetIDs.GetAllSubnets()
42}
43
44func (_ *Service) aggregatorSubnetIndices(currentSlot primitives.Slot) []uint64 {45 endEpoch := slots.ToEpoch(currentSlot) + 1
46 endSlot := params.BeaconConfig().SlotsPerEpoch.Mul(uint64(endEpoch))
47 var commIds []uint64receiver name should not be an underscore, omit the name if it is unused
37 return s.cfg.attPool.SaveUnaggregatedAttestation(a)
38}
39
40func (_ *Service) persistentSubnetIndices() []uint64 {41 return cache.SubnetIDs.GetAllSubnets()
42}
43
Description
The name of a method's receiver should be a reflection of its identity; often a one or two letter abbreviation of its type suffices (such as "c" or "cl" for "Client").
Don't use generic names such as "me", "this" or "self", identifiers typical of object-oriented languages that place more emphasis on methods as opposed to functions. The name need not be as descriptive as that of a method argument, as its role is obvious and serves no documentary purpose. It can be very short as it will appear on almost every line of every method of the type; familiarity admits brevity. Be consistent, too: if you call the receiver "c" in one method, don't call it "cl" in another.
Bad practice
type something int
func (this something) foo() {}
Recommended
type something int
func (s something) foo() {}