{"push_id":2621410626,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"2d5fdfa798f54f96ae328aca2e5b6401b89949c7","before":"a90f3602e33faad952c5524bcefe3e43bd5201b4","commits":[{"sha":"2d5fdfa798f54f96ae328aca2e5b6401b89949c7","author":{"name":"Soumya","email":"2913f5af13f0e6119c36cfd542ade482548ebb91@google.com"},"message":"Use *Segment instead of Segment, remove unneeded wrapping struct\n\nThe only reason the struct existed was to give Segment{} pointer semantics by wrapping a pointer to the actual data. Exported pointer types are present in stdlib, so using exported pointer to Segment is fine.\nExporting the Segment type but using it as a pointer also has the advantage of allowing a zero-value &Segment{}, while in the previous case, Segment{} would panic because of the nil reference to data.\nIt makes the potential race condition more explicit as well, since we're sending a pointer over the output channel, but in most cases that pointer is never accessed by the sender again, so it's a minor concern. This race was already present, but harder to track down because of the struct {*data} wrapper.","distinct":true,"url":"https://api.github.com/repos/soumya92/barista/commits/2d5fdfa798f54f96ae328aca2e5b6401b89949c7"}]}
{"actor":{"display_login":"soumya92"}}