Closed InsaneDoggo closed 4 years ago
Hi. It was maid to guarantee proper initialization and clearing of the property. It can be replaced with own synchronization inside ViewBindingPropertyDelegate
. I’ll think about that
Instead of your case I prefer to do next
with(binding) {
textView1.text = "blabla"
textView3.text = "blabla"
textView2.text = "blabla"
}
Instead of your case I prefer to do next
with(binding) { textView1.text = "blabla" textView3.text = "blabla" textView2.text = "blabla" }
iirc compiler will unwrap it into my example (three independent calls)
Will be changed in 1.2.3
Hi, nice lib. Isn't checkIsMainThread redundant? Android framework already has a lot of checks. You will got an exception if trying to touch views from another thread.
Consider next snippet:
Looper.getMainLooper() contains synchronized block, seems like overhead for mentioned above case.