Welp, I’ve just tried to update support library to 27.0.1 version from 26.1.0 and got a whole bunch of nullability errors because a lot of methods like

getActivity

in Fragment got

@Nullable

annotation. But what should I do now in following situations? For example, I build DialogFragment. I need a context in

onCreateDialog

method. To do something like this:

return MaterialDialog.Builder(context)
                .title(R.string.invitation_to_team_dialog_title)
                .content(buildDescriptionText())
                .build()

onCreateDialog

method must return NonNull Dialog instance so I can’t use

context?.let

call. And I really doubt context may be null on this stage (as well as activity in Fragment’s

onCreateView

method, I suppose?). So I forced to use ugly

!!

call. @jw as I know from your twitter these annotations were your endeavor. So, from your opinion, what should be an intended workaround in this situation? I don’t really like double exclamation point. It looks like very Java-ish way to care about nullability, sort of “I don’t care, whatever”

That's too much boilderplate for me

agree, but if “I don’t really like double exclamation point” explicit error handling could be solution. Particularly for this case I prefer

!!

, but for cases when you can just return from function just easier to do that:

val context = context ?: return

Yeah it depends