{"push_id":891823145,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"8c55a0e0abbc4d0e0a2ee18ba5654534dfffb9f5","before":"6034b4a706f205df97ba7aa63ea3c706ced8c247","commits":[{"sha":"8e6b6413c9054a6f8fbd9dfd84f5dc6b96da0360","author":{"email":"85d5c8dcb7db39358916efb7e6f840502f547b2c@lazarenko.me","name":"Vlad Lazarenko"},"message":"Add EXPECT_NE, EXPECT_TRUE and EXPECT_FALSE macros.","distinct":true,"url":"https://api.github.com/repos/ul1tka/fix/commits/8e6b6413c9054a6f8fbd9dfd84f5dc6b96da0360"},{"sha":"92560039bca2c7267304a320d49a1125ad2e92d4","author":{"email":"85d5c8dcb7db39358916efb7e6f840502f547b2c@lazarenko.me","name":"Vlad Lazarenko"},"message":"Parser impovements.\n\n - Add FIX_PARSE_BEGIN_WITH macro that can be used if user knows\n   from what tag it begins the parsing (i.e. start at 35, not 8).\n - Parser BEGIN/END macros put everything inside its own scope.\n\nEven with the scope, there is still a problem with conflicting\njump labels, so code for parsing different messages cannot appear\nin a single function.","distinct":true,"url":"https://api.github.com/repos/ul1tka/fix/commits/92560039bca2c7267304a320d49a1125ad2e92d4"},{"sha":"44801784b9a990a3e9f111f40e7909bc351ce5e3","author":{"email":"85d5c8dcb7db39358916efb7e6f840502f547b2c@lazarenko.me","name":"Vlad Lazarenko"},"message":"Add FIX_COLD.\n\nAlso switch to using special __FOO__ attributes just in case\nsome users define some of that stuff themselves, which may confuse\nthe compiler (better safe than sure).","distinct":true,"url":"https://api.github.com/repos/ul1tka/fix/commits/44801784b9a990a3e9f111f40e7909bc351ce5e3"},{"sha":"8c55a0e0abbc4d0e0a2ee18ba5654534dfffb9f5","author":{"email":"85d5c8dcb7db39358916efb7e6f840502f547b2c@lazarenko.me","name":"Vlad Lazarenko"},"message":"Add FIX stream parser.\n\nBasically, its goal is to parse variable-length streams (i.e.\nTCP/IP data stream) and quickly detect FIX message begin/end\nso that message can be parsed with fix_parse_* API.\n\nIt is optimized for zero-copy. Meaning that if message is\nreceived as a whole and not in parts, no extra data copies\nare made.\n\nIn case when some of the messages is received in part while\nother are received as a whole, only a minimal subset of\nmemory is copied in order to represent a chopped and\nreconstructed message continuously in memory.","distinct":true,"url":"https://api.github.com/repos/ul1tka/fix/commits/8c55a0e0abbc4d0e0a2ee18ba5654534dfffb9f5"}]}