RFC NNNN: Title¶

Summary¶

One paragraph describing the change.

What problem does this solve, and for whom? Include measurements or concrete examples where they exist. Explain why the problem is worth solving now.

Describe the change in enough detail that someone familiar with Wybthon could implement it. Cover:

the public API, with signatures and short examples;
the runtime behavior and the contracts it relies on or changes;
how it interacts with existing features (reactivity, ownership, the kernel, the router, the build);
error handling and dev-mode diagnostics.

List every public API that's removed, renamed, or changes behavior, and what replaces it. Write "None" if there aren't any.

What else did you consider, and why didn't you choose it? Include "do nothing."

What does this cost in complexity, performance, bundle size, or maintenance? What could go wrong?

How will the change be verified? Name the unit tests, browser tests, benchmarks, or work gates involved.

What's still open? What's deliberately left for later RFCs?

Filled in by a maintainer when the RFC is accepted or rejected.