seriously though, I bet 80% of the people who use ...
# random
k
seriously though, I bet 80% of the people who use
lazy
aren't aware of the locking. I raised the issue during milestone phase but it didn't lead to any solution
k
Well it's not really a bad idea to have it be syncronized by default, what would you have wanted instead?
k
that's the tough question. what's the better default and how to emphasize the implications
l
I think the issue is that you’re fine with
NONE
in 90% of the cases on Android. However, on “normal” (e.g. backend) apps, that’s not so simple. So synchronized is probably the best default. Maybe it’s a good idea to improve tooling. Something “this lazy delegate could use
LazyThreadSafetyMode.NONE
” (I get that that’s really hard to figure out.)