<@U6Y33L3ME> these are nested not inner classes, a...
# announcements
p
@edwardwongtl these are nested not inner classes, and they can reference each other’s constructor just fine in general (only a problem with
sealed
)
e
Well nested class pretty much means inner class, the thing that matters is your
Foo
is inside
Outer
. If
Foo
is not inside
Outer
,and it become a stand alone class at file level, then you don't need to put the child class in
{}
p
nested is not the same as inner in kotlin and java. anyway, I’m trying to understand if the current behavior is intentional and if so, what the rationale is. I’m aware of the workarounds.