Kotlin中‘!!’（双感叹号）与‘as’类型转换是否等效？

Great question! At first glance, both text!! and text as String seem to do the same thing: convert a nullable String? to a non-null String and throw an exception if text is null. But they're not fully equivalent—let's break down the key differences:

1. Different exception types when text is null #

• text!! throws a KotlinNullPointerException—this is a Kotlin-specific exception designed explicitly for null assertion failures, making it clear the crash came from a null value being accessed despite a non-null guarantee.
• text as String throws a ClassCastException—the standard exception for invalid type conversions. Under the hood, casting a null of type String? to String is treated as a failed type cast, hence this exception type.

2. Semantic meaning and compiler behavior #

• !! is a dedicated null assertion operator. Its only job is to tell the compiler: "I promise this nullable value isn't null—treat it as non-null." It only cares about nullity, not type mismatches (as long as the underlying type matches the non-null variant).
• as is a type cast operator. When you use text as String on a String? variable, you're performing an unchecked cast from the nullable type to the non-null type. The compiler will even warn you about this (Unchecked cast: String? to String) because it can't verify the cast at compile time.
• For broader nullable types (like Any?), the difference is even starker:

  var nullableAny: Any? = "hello"
  // !! asserts non-null, but you still need a cast to get a String
  val str1 = nullableAny!! as String 
  
  var nullableAnyNull: Any? = null
  nullableAnyNull!! // Throws KotlinNullPointerException immediately
  nullableAnyNull as String // Throws ClassCastException immediately
  

3. Intent clarity #

• Using !! makes your intent explicit to other developers: you're intentionally asserting that a nullable value is non-null.
• Using as String for a String? variable is less idiomatic—it feels like a workaround that leverages type casting, rather than clearly communicating your null assertion intent.

So while both operations will crash when text is null, they differ in exception type, semantic purpose, and behavior in edge cases. They're not interchangeable in all scenarios.

内容的提问来源于stack exchange，提问作者Wojtek