moonbit_image.internal_test.c
moonbit_image.blackbox_test.c
  正在创建库 D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\_build\native\debug\test\moonbit_image.blackbox_test.lib 和对象 D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\_build\native\debug\test\moonbit_image.blackbox_test.exp
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib.mbt:149:14 ]
     │
 149 │       match (try? decode_by_format_raw(data, format)) {
     │              ──┬─  
     │                ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib.mbt:164:10 ]
     │
 164 │   match (try? decode_by_format_raw(data, format)) {
     │          ──┬─  
     │            ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib.mbt:201:14 ]
     │
 201 │       match (try? image_dimensions_raw(data, format)) {
     │              ──┬─  
     │                ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib.mbt:341:14 ]
     │
 341 │       match (try? encode_bmp(img)) {
     │              ──┬─  
     │                ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib.mbt:346:14 ]
     │
 346 │       match (try? encode_qoi(img)) {
     │              ──┬─  
     │                ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib_test.mbt:148:44 ]
     │
 148 │   let bogus : Result[Image, DecodeError] = try? decode(b"definitely not an image")
     │                                            ──┬─  
     │                                              ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0020]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\lib_test.mbt:158:40 ]
     │
 158 │   let r : Result[Image, DecodeError] = try? decode(
     │                                        ──┬─  
     │                                          ╰─── Warning (deprecated): `try?` is deprecated.

  Do not mechanically replace this with `try expr |> Ok catch { e => Err(e) }`; that still creates a local `Result` wrapper and usually misses theintended migration.
  Only create `Ok`/`Err` when the `Result` value must escape this local expression: stored, returned, passed to a Result-taking API, or kept for later comparison as data.

  Migration in inspect-based tests:
  1. If the expected behavior is success, remove `try?` and run the raising expression directly:

    inspect(expr, content=...)

  2. If the expected behavior is an error, replace `try?` with `try ... catch ... noraise`:

    try expr catch {
      e => inspect(e, content=...)
    } noraise {
      _ => fail("expected expr to raise")
    }

─────╯
Warning: [0002]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\tiff.mbt:147:7 ]
     │
 147 │ const TAG_ROWS_PER_STRIP : Int = 278
     │       ─────────┬────────  
     │                ╰────────── Warning (unused_value): Unused variable 'TAG_ROWS_PER_STRIP'
─────╯
Warning: [0007]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\tiff.mbt:166:3 ]
     │
 166 │   typ : Int
     │   ─┬─  
     │    ╰─── Warning (unused_field): Field 'typ' is never read
─────╯
Warning: [0007]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\tiff.mbt:167:3 ]
     │
 167 │   count : Int
     │   ──┬──  
     │     ╰──── Warning (unused_field): Field 'count' is never read
─────╯
Warning: [0051]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\tiff.mbt:222:36 ]
     │
 222 │         1 | 2 => base >> (pos * 8) & 0xFF
     │                                    ┬  
     │                                    ╰── Warning (ambiguous_precedence): Operator `>>` and `&` are ambiguous, add parenthesis to disambiguate.
─────╯
Warning: [0051]
     ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\tiff.mbt:223:36 ]
     │
 223 │         3 => base >> (pos * 2 * 8) & 0xFFFF
     │                                    ┬  
     │                                    ╰── Warning (ambiguous_precedence): Operator `>>` and `&` are ambiguous, add parenthesis to disambiguate.
─────╯
Warning: [0006]
    ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\types.mbt:36:3 ]
    │
 36 │   ICO
    │   ─┬─  
    │    ╰─── Warning (unused_constructor): Variant 'ICO' is never constructed
────╯
Warning: [0006]
    ╭─[ D:\src\MiniMax\Projects\MoonBit\moonbit-labeler\staging-moonbit-image\types.mbt:38:3 ]
    │
 38 │   TIFF
    │   ──┬─  
    │     ╰─── Warning (unused_constructor): Variant 'TIFF' is never constructed
────╯
[riantr/moonbit_image] test lib_test.mbt:169 ("blackbox: image_dimensions reads PNG IHDR without decoding pixels") failed: lib_test.mbt:176:10-176:50@riantr/moonbit_image FAILED: image_dimensions raised an error
[riantr/moonbit_image] test lib_test.mbt:203 ("ico: detect_format picks up Windows ICO header") failed: lib_test.mbt:208:13-208:51@riantr/moonbit_image FAILED: detect_format missed ICO magic
[riantr/moonbit_image] test lib_test.mbt:238 ("tiff: detect_format picks up little-endian TIFF header") failed: lib_test.mbt:243:14-243:71@riantr/moonbit_image FAILED: expected TIFF, got None
Total tests: 40, passed: 37, failed: 3.
