@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
So, we've looked at it again based on two factors: avoid breaking existing Kotlin code, and follow the principle of least surprise -- the code should work just as you expect it to. /10
@relizarov ("Roman Elizarov") replied to a tweet by @relizarov:
So, we've looked at it again based on two factors: avoid breaking existing Kotlin code, and follow the principle of least surprise -- the code should work just as you expect it to. /10