{"push_id":1155584358,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a8743b62bb6a50bb1f65a720a1ca8006e2b2cc79","before":"58d190bb004aab169d9fd737c0af80d6c7b1258b","commits":[{"sha":"a8743b62bb6a50bb1f65a720a1ca8006e2b2cc79","author":{"name":"Michael Younkin","email":"fe8dc460e648b6b0a9420ebb48f6848758fb43f9@gmail.com"},"message":"Return to my original approach for parsing\n\nI was trying to do too much, which was fine because I learned a lot about the\n\"easy way\" and \"hard way\" to do things in Rust in the process. I tried a bunch\nof C idioms (like casting a byte array to a struct) that are really annoying in\nRust - and that's okay!\n\nAll the best practices will probably change pretty soon since they're adding\nthigns like const fn and untagged union's (untagged unions in particular would\nbe useful for networking applications). Better support for unsized structs would\nalso be really nice. At the moment, I've given up on my \"buffering\" design and\nam just going to copy data around until I get more of the protocol implemented.\nPerhaps at that point I'll be able to do something more interesting.\n\nAnother benefit of waiting to eliminate copying is I can make sure to only do it\nwhere it's affecting performance :). My goal is to beat ENet, which shouldn't be\ntoo hard to do since it's using linked lists everywhere.","distinct":true,"url":"https://api.github.com/repos/michael-younkin/rustynet/commits/a8743b62bb6a50bb1f65a720a1ca8006e2b2cc79"}]}
{"actor":{"display_login":"michael-younkin"}}