{"push_id":1696870885,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"c5107527a41b9168d093bf9dd2f18be79654e3b9","before":"b3e721100184debc3bebf556da3ba536e4a2fb50","commits":[{"sha":"c5107527a41b9168d093bf9dd2f18be79654e3b9","author":{"name":"Slipp Douglas Thompson","email":"5bf00c93c9250d44d769b81890fa6584403ae7e0@capnslipp.com"},"message":"Made all other constructors use `init(_:,_:,_:)`\n\nFormerly, I had many of the constructors calling `init(tuple:)`, which now strikes me as inefficient wrapping and unwrapping.\n\n* Switched each `init` to internally call `init(_:,_:,_:)`.  \n\t‣ Theoretically, the Swift compiler should be smart enough to optimize the extra level of calling out and just run the `var` assignments.  All these qualify for TCO, afterall.  \n\t‣ Exception, the zero-arg `init()`, which calls `init(_ scalar:)` _(which in turn calls `init(_:,_:,_:)`)_.\n* Bumped version to `1.2.1`.","distinct":true,"url":"https://api.github.com/repos/capnslipp/Int3/commits/c5107527a41b9168d093bf9dd2f18be79654e3b9"}]}
{"actor":{"display_login":"capnslipp"}}