The only safe way is just to pass the context to whatever function needs it, now you know it’s always the correct one

otherwise, you’re just setting yourself up for some obscure bugs that will only happen once your app is in production

or anywhere, really. a lot of libraries which maintain internal singletons do this https://kotlinlang.slack.com/archives/android/p1449676320001468

in one-process environment you're bound to have one and only one application context. i'm talking here only about app context. referencing other contexts (from activity or service) will surely cause memory leak

if you're not inflating views then storing an app context is fine

Still learning here, but is it possible to use the stdlib, "apply" in this manner...

@dharrigan: you could, but what's the point?

Testing my understanding - the findFragmentByTag returns the fragment or null if not found, so the ?.apply will only "apply" if it is not null. Question remains, the object returned by findFragmentsByTag (a Fragment), how would I access it within the apply block (or indeed, if it is accessible...I'm assuming it's the "this")?

isVisible

is a getter, isn’t it a no op to do that?

Usually,

apply

contains side effect stuff, e.g. setters

I see I see

then it returns the receiver

Is there a better, more Kotlin-idomatic way of achieving what I want?

Typically:

findWindow().apply {
  width = 100
  height = 100
}

Do you just want to see if it’s visible? Just call

?.isVisible

on the returned instance

Screen Shot 2015-12-09 at 18.04.52.png

the API for findFragmentsByTag suggest it returns null if nothing found.

maybe you're looking for run{}?

-.java

that looks interesting

or even

let {}

I don’t think run will help you there, what you want is

if (fragment?.isVisible!!)

/me has to look up the !! explanation again simple smile

hmm, let is intersting too

let

is fine for 1) scoping and 2) when you need an

if

without an

else

if (fragment?.isVisible!!)

this will probably throw an NPE when fragment is null

Yeah

Not good