0

Understandably the asterisk symbol (import androidx.compose.material3.*) imports all resources, but is it more or less efficient and resource-hungry than only using the imports a project needs? e.g. using several imports instead of *.

Scenario 1

import androidx.compose.material3.*

Scenario 2

import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.MediumTopAppBar
import androidx.compose.material3.Scaffold
import androidx.compose.material3.Surface
import androidx.compose.material3.Text
wbk727
  • 8,017
  • 12
  • 61
  • 125
  • Have a look here: https://stackoverflow.com/a/13980664/13598222 – cactustictacs May 04 '22 at 23:59
  • Does this answer your question? [Does an import wildcard import everything all the time?](https://stackoverflow.com/questions/13980580/does-an-import-wildcard-import-everything-all-the-time) – Abhimanyu May 05 '22 at 01:37

1 Answers1

0

It is efficient. Android Studio will import named classes until they become too many, in which case it will default to importing all under the concerned package. The thing is, during build (final release i), checks are in place to ensure all unused resources are kept from being packaged in the build. Something like minifyEnabled in the build files also does something similar. Even if they do end up getting packaged, it is still fine. That is because they are just a bunch of text files that weigh KBs, which are further compressed during the build to less than you'd expect. So, there's no practical paranoia here that those would bloat your apk. Relax,

Richard Onslow Roper
  • 5,477
  • 2
  • 11
  • 42