Paano mai-agapan ang wakas ng karanasan at ang pagkakaiba ng tsek / unchecked?

Question

Accepted Answer

Java tana da bugi da **`try`/`catch`/`finally`**, kuma ya bambanta kayan gaske **jecint exceptions** (dole ne a bayyana ko sa wariya) da daga **unchecked exceptions** (lokaci na aiki, ba bukatowa ba). Fahimtar wannan bambantacciyar muhimmin aiki ne na sarrafa bugi a Java.

## Tsarin gida

```java
try {
    FileReader f = new FileReader("file.txt");   // may throw IOException
    // ... use it ...
} catch (FileNotFoundException e) {
    System.out.println("not found: " + e.getMessage()); // specific first
} catch (IOException e) {
    System.out.println("io error");                      // broader after
} finally {
    System.out.println("always runs — cleanup");         // runs no matter what
}
```

`finally` koyaushe na aiki (tsaftace), ko da ma exception an jefawa ko `return` ya faru.

## Tsarin ra'ayin exceptions

```text
Throwable
  ├── Error            — serious JVM problems (OutOfMemoryError) — don't catch
  └── Exception
        ├── RuntimeException  → UNCHECKED (not enforced by the compiler)
        │     NullPointerException, IllegalArgumentException, IndexOutOfBounds...
        └── (other Exceptions) → CHECKED (compiler enforces handling)
              IOException, SQLException...
```

## Jecint exceptions — tilasta da mai-mahimmin su

```java
// MUST either catch it or declare `throws` — the compiler won't let you ignore it
public void readFile() throws IOException {   // declare it
    Files.readAllLines(Paths.get("file.txt")); // throws checked IOException
}
```

**Jecint exceptions** (IOException, SQLException) sun nuna da kariya, abin da ake sa ran (fayil da babu, gadewa na sadarwa). Compiler ya *tilasta** ka wariya su ko bayyana su — sarrafa barge na wajen ta jajaniya.

## Unchecked exceptions — lokaci na aiki, ba bukatowa ba

```java
// NOT required to declare or catch — usually indicate PROGRAMMING BUGS
String s = null;
s.length();                       // NullPointerException (unchecked)
int x = arr[10];                   // ArrayIndexOutOfBoundsException (unchecked)
Integer.parseInt("abc");           // NumberFormatException (unchecked)
```

**Unchecked** (ƙananan nanowar RuntimeException) yawanci suna nuna bugi na programa — kana gyara bugi maimakon ya taba duwatsu a gaida. Compiler ba bukatowa ya wariya.

## try-with-resources (tsaftace kai tsaye)

```java
// resources implementing AutoCloseable are closed automatically
try (FileReader f = new FileReader("file.txt")) {
    // use f
}   // f.close() called automatically, even on exception — no finally needed
```

## Kyau kyau na aiki

```text
✓ Catch specific exceptions, not bare Exception
✓ Use try-with-resources for files/connections (auto-close)
✓ Don't swallow exceptions silently (empty catch blocks)
✓ Throw meaningful exceptions; include context in messages
✓ Custom exceptions extend Exception (checked) or RuntimeException (unchecked)
```

## Me yasa ya zama muhimmin

Dabarun wariya mai kariya ya zama muhimmi, kuma **bambantacciyar jecint/unchecked na Java ta yi kira (kuma ana jaje) halaye** da ya kamata a fahimta sosai.

Jecint exceptions suna tilasta sarrafa sakanda na wajen da ake sa ran (I/O, DB) — haɓaka tabbatacciya amma wani lokaci ana ta jaje a matsayin magana; unchecked exceptions suna nuna bugi don gyara maimakon ya taba duwatsu a gaida.

Sanin jajagen, lokaci kowane nau'i zai yi amfani, `try/catch/finally` ma'ana, kuma **try-with-resources** na zamani don tsaftace kai tsaye ya zama mahimmi don rubuta daidai, tabbatacciyar Java — kuma tsara kanunka ta asada dabam.

Bambantacciyar ta sarrafa yadda aka tsara Java APIs kuma shine lokaciwa baje jaye sha.