fzyzcjy

00:00 +0: loading /Users/tom/.codex/worktrees/942d/flutter_rust_bridge/frb_example/native_assets_hook_overhead_fixture/test/a_test.dart
00:00 +0: /Users/tom/.codex/worktrees/942d/flutter_rust_bridge/frb_example/native_assets_hook_overhead_fixture/test/a_test.dart: a
00:00 +1: /Users/tom/.codex/worktrees/942d/flutter_rust_bridge/frb_example/native_assets_hook_overhead_fixture/test/a_test.dart: a
00:00 +2: All tests passed!

fzyzcjy

ch3.1 op40/op42 mechanical-move proofs (post-merge, linear chain)

Re-authored after merging latest upstream/main into the ch3.1 chain and relinearizing it (each op branch = pre-merge commit count on top of main, no merge commits). Every mechanical move below reproduces its commit byte-for-byte from the base commit via the faithful relocation primitives in mechanical_refactor_reproduction_utils.py (the engine from the mechanical-refactor-verify skill), then runs pre-commit and diffs against the target. Empty diff = PASS.

Proofs (all PASS)

fzyzcjy

#!/usr/bin/env python3
"""op42 mechanical move (spec decode): extract the canonical de-batched alloc block from
eagle_prepare_for_decode into a module-level alloc_for_spec_decode in mem_cache/allocation.py.
The body is cut verbatim by extract_function; only signature / call are authored."""
import subprocess
import sys

sys.path.insert(
    0,
    str(__import__("pathlib").Path(__file__).resolve().parent),

fzyzcjy

#!/usr/bin/env python3
"""op42 mechanical move (decode prealloc): extract the two prealloc alloc blocks in
DecodePreallocQueue into module-level free functions alloc_for_decode_prealloc_hisparse
and alloc_for_decode_prealloc. Bodies are cut verbatim by extract_function; only the
signature / return / call interface is authored."""
import subprocess
import sys

sys.path.insert(
    0,

fzyzcjy

"""Auto-generated reproduce script. Audit each call, then run.

commit:  d9e21ed5bb90650c8497c874c59f6eb7ad20c5ba
subject: Relocate assign_req_to_token_pool triton helpers into mem_cache/allocation.py

Each call is a faithful relocation primitive. Running this reproduces the commit
in a throwaway worktree and diffs it byte-for-byte; PASS means the commit is
exactly these relocations.
"""
import sys

fzyzcjy

"""Auto-generated reproduce script. Audit each call, then run.

commit:  65cfba81f5c69178e743100ff0a5b55b402b4dc8
subject: Lightweight extract allocation logic from mem_cache/common.py to more clearly show nearly parallel variants

Each call is a faithful relocation primitive. Running this reproduces the commit
in a throwaway worktree and diffs it byte-for-byte; PASS means the commit is
exactly these relocations.
"""
import sys

fzyzcjy

{
  "page": {
    "url": "https://cjycode.com/flutter_rust_bridge/demo/",
    "title": "",
    "text": "Skip to main content\nFlutter Rust Bridge\nv2\nGitHub\nSearch\n⌘\nK\nIntroduction\nQuickstart\nDemo\nGuides\nOverview\nTypes\nTwo-way Road\nFunctions\nTraits (base classes)\nTranslate third-party packages\nLifetimes / Return references\nConcurrency and async\nCustomization\nCross-platform utils\nMisc Features\nMiscellaneous\nHow-to\nWho is using it\nPerformance\nContributor guide & Implementations\nManual (76 entries)\nDemo\nDemo\n\nSome scenarios when using Rust and Dart include:\n\nUse arbitrary Rust libraries, in Dart: When there is a library only existing in Rust but not in Dart.\nHigh-performance code in Rust, others in Dart: Rust makes it easy to write multi-thread code, algorithms, data-intensive operations, etc.\nLogic in Rust, UI in Dart: When you want a UI framework (Flutter) for your Rust system.\nIntroduction​\n\nWe demonstrate a simple example here. In this demo, let us draw a Mandelbrot set (a

fzyzcjy

#!/usr/bin/env python3
"""Reproducible transform for: extract release_req / retract_all as module-level free functions.

Run from the sglang repo root:
    python3 /tmp/transform_release_req_free_func.py
"""
import sys
from pathlib import Path

sys.path.append(".claude/skills/mechanical-refactor-verify")

fzyzcjy

#!/usr/bin/env python3
"""Programmatic byte-equality audit for PR #26271
(sgl-project/sglang `tom/scheduler_init_style`).

The PR claims to be a purely mechanical refactor of
``python/sglang/srt/managers/scheduler.py``: 13 inline component
constructions inside ``Scheduler.__init__`` are extracted into
per-component ``init_<name>()`` methods, with no behavior change.

This script proves the claim by *programmatic* comparison instead of

fzyzcjy

# SPDX-License-Identifier: Apache-2.0

import json
import os
import sys
import time
import traceback
from dataclasses import dataclass, field
from typing import List, Optional, Union