| 59229481aec5a284d322a2ca80dff836485feb0c |
|
30-Oct-2015 |
Yigit Boyar <yboyar@google.com> |
upgrade kotlin to 1.0-beta1
Change-Id: I62b77fd118e2715d272a16d96b9083d2347f5fb1
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/ext/ext.kt
|
| fda1703c88eb22e9f166d957d6bda2cd8d645b8f |
|
11-Jun-2015 |
Yigit Boyar <yboyar@google.com> |
Upgrade kotlin to 0.12.412
Bug: 21756156
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/ext/ext.kt
|
| 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/kotlin/android/databinding/tool/ext/ext.kt
|
| fead9ca09b117136b35bc5bf137340a754f9eddd |
|
23-Mar-2015 |
George Mount <mount@google.com> |
Move to package android.databinding.
/frameworks/data-binding/compiler/src/main/kotlin/android/databinding/tool/ext/ext.kt
|