{"push_id":652047538,"size":2,"distinct_size":2,"ref":"refs/heads/Go","head":"75ef112513b7eafb285dc14c0a41759544a766b8","before":"fa5273139839e16ba21ce1c0d3248768c34ac660","commits":[{"sha":"3b2b2259b78ae4434ecac41217a18e67c46e9762","author":{"email":"b04003fa1d41b72a2c226772d58f3356a9712618@felipes-mbp.attlocal.net","name":"Felipe Robledo"},"message":"So I changed the 2D points file to implement an interface. However, now I see that instead of writing my own printing functions, I could have\nimplemented the Stringer interface's String() string function to let stdout know how to print a vertex. That is kind of neat :). We can have interfaces in 1 file, and anything else that implements it anywhere else. However, doesn't this increase compile time? Is it not hard for the linker to verify that all the dependencies between types and interface implemented methods? This seems like a big can of worms.","distinct":true,"url":"https://api.github.com/repos/ProjectDestiny/Portafolio/commits/3b2b2259b78ae4434ecac41217a18e67c46e9762"},{"sha":"75ef112513b7eafb285dc14c0a41759544a766b8","author":{"email":"b04003fa1d41b72a2c226772d58f3356a9712618@felipes-mbp.attlocal.net","name":"Felipe Robledo"},"message":"small go routine example. Haven't tried channels, but they seem easy enough.","distinct":true,"url":"https://api.github.com/repos/ProjectDestiny/Portafolio/commits/75ef112513b7eafb285dc14c0a41759544a766b8"}]}