{"push_id":888440702,"size":4,"distinct_size":4,"ref":"refs/heads/inc-comp-stable-self","head":"b0f4d33243ea8e05b0633de96a05441f27937a94","before":"c779e567b25e3578d3d10de139ce495c221b8981","commits":[{"sha":"3da6d837d2b9a201bbf8f56638d233953bf15d64","author":{"email":"7639fe603eb93a42390376ac4f0d54260fa6a394@typesafe.com","name":"Adriaan Moors"},"message":"compile on scala 2.10.6 and java 1.7","distinct":true,"url":"https://api.github.com/repos/adriaanm/sbt/commits/3da6d837d2b9a201bbf8f56638d233953bf15d64"},{"sha":"ea54df681e2a074a1749b57e031ad7c9a1f60456","author":{"email":"7639fe603eb93a42390376ac4f0d54260fa6a394@typesafe.com","name":"Adriaan Moors"},"message":"clean up show api implicit overload\n\nadd rough cycle detection / diagnosis -- should that cycle be there??\nwhat's the original type representation in scalac?\n\n```\nclass Dep {\n  // the result type for this method contains a cyclic existential type that blows up show api in name hashing debugging\n  def bla(c: Boolean) = if (c) new Value else \"bla\"\n}\n\nclass Value extends java.lang.Comparable[Value] { def compareTo(that: Value): Int = 1 }\n```","distinct":true,"url":"https://api.github.com/repos/adriaanm/sbt/commits/ea54df681e2a074a1749b57e031ad7c9a1f60456"},{"sha":"41aa3ea3eeb00ee02cc5d028df2ca9d6b65361ef","author":{"email":"7639fe603eb93a42390376ac4f0d54260fa6a394@typesafe.com","name":"Adriaan Moors"},"message":"avoid BTS for refinement types, as they can get huge\n\nTODO: do we need them? we also skip inherited members, so i assume just tracking parents is ok","distinct":true,"url":"https://api.github.com/repos/adriaanm/sbt/commits/41aa3ea3eeb00ee02cc5d028df2ca9d6b65361ef"},{"sha":"b0f4d33243ea8e05b0633de96a05441f27937a94","author":{"email":"7639fe603eb93a42390376ac4f0d54260fa6a394@typesafe.com","name":"Adriaan Moors"},"message":"Only include all base types for class definitions\n\nFor refinement types, the Structure was already restricted\nto declarations (and not inherited members), but all base types\nwere still included for a refinement's parents, which would\ncreate unwieldy, and even erroneous (cyclic) types by expanding\nall constituents of an intersection type to add all base types.\n\nSince the logic already disregarded inherited members, it seems\nlogical to only include direct parents, and not all ancestor types.","distinct":true,"url":"https://api.github.com/repos/adriaanm/sbt/commits/b0f4d33243ea8e05b0633de96a05441f27937a94"}]}