Further, any news regarding the package-protected ...

# language-proposals

[GreyhairRedbear]

Further, any news regarding the package-protected visibility (https://discuss.kotlinlang.org/t/kotlin-to-support-package-protected-visibility/1544/55 and https://youtrack.jetbrains.net/issue/KT-29227)?

[Ruckus]

Hah! Sorry, my comment wasn't a counter to yours, just a funny coincidence.

[GreyhairRedbear]

XD nevermind

[karelpeeters]

Can you elaborate a bit on the weak reference? Who has a weak reference to what?

[GreyhairRedbear]

E.g. when you pass a lambda instead of a SAM interface to a function, this newly created anonymous object will hold a strong reference to the encapsulating class.

When using Swift, it is possible to explicitly specify [weak self] in the list of arguments the lambda (or closure, as its called in swift) captures, which causes the reference to the encapsulating object to be a weak one.

[karelpeeters]

Ah you want a reference to the lambda itself?

[GreyhairRedbear]

No, I don't. I want the reference a lambda usually captures to the enclosing class to be a weak one.

someFunctionThatTakesAClosure { [weak self] in print($0) }

Taken from the last section of this (https://stackoverflow.com/a/42275638/4929939) stackoverflow answer.

[gildor]

This is wrong slack channel to ask about feature status