Cross Reference: /frameworks/data-binding/compiler/src/main/java/android/databinding/tool/expr/VersionProvider.java

History log of /frameworks/data-binding/compiler/src/main/java/android/databinding/tool/expr/VersionProvider.java
Revision		Date	Author	Comments (<<< Hide modified files) (Show modified files >>>)
af146d6a8c0efcf5682d14047c06866a5548f78f		22-Jan-2016	Yigit Boyar <yboyar@google.com>	Update data binding to kotlin beta 4 I've also run some cleanup inspections to keep codebase more up to date. Bug: 26738574 Change-Id: I02aa43157cad858c0ea60dd41a22150e3cf2cfa1 /frameworks/data-binding/compiler/src/main/java/android/databinding/tool/expr/VersionProvider.java
7b07818f07c28c6dec34ca2a9ab5f61e86afb493		20-May-2015	Yigit Boyar <yboyar@google.com>	Handle inter-expr dependencies properly We had a bug where we would never be able to solve a case if there are two expressions that trigger a circular dependency. a ? b : c b ? a : d We actually had some logic to partially elevate conditional dependencies but there were two issues with it: * LayoutInflator was caching shouldReadFlags permanently * There was a bug in how we resolve whether all potential evaluation paths are covered. (we were not using a cloned bitset but rather updating the original). I've fixed these two issues and added logic to partially elevate conditional expressions if they cannot be marked as fully read. Bug: 21324645 Change-Id: I779afb6dae48920196404d3cfbb5f8774686404d /frameworks/data-binding/compiler/src/main/java/android/databinding/tool/expr/VersionProvider.java