AssemblyScript¶
These real terminal captures use a historical development build. They are not current release certification; independent output review and current installed-wheel scenario checks remain pending.
Overview¶
This worked example compares code.as. Advertised filename extensions: .as.
What changes¶
Keep add unchanged, change square from nn to n2, and add exported cube returning n*3.
Before¶
export function add(a: i32, b: i32): i32 {
return a + b;
}
export function square(n: i32): i32 {
return n * n;
}
After¶
export function add(a: i32, b: i32): i32 {
return a + b;
}
export function square(n: i32): i32 {
return n ** 2;
}
export function cube(n: i32): i32 {
return n ** 3;
}
Things to know¶
-
Integer exponentiation versus multiplication equivalence, overflow and compiler support are not independently executed here.
-
The .as extension is ambiguous outside explicitly selected AssemblyScript routing.
Recorded output¶
Recorded from a real native CLI through rs-rich-record. A refactoring label does not prove equivalent behavior. Build identities.
Scenario coverage¶
| Scenario | Status |
|---|---|
| Meaningful edit | Source example reviewed; output captured; independent result certification pending |
| Unchanged content | Not yet certified for this candidate |
| Populate / clear a file | Not yet certified for this candidate |
| Add / delete an entity | Not yet certified for this candidate |
| Rename a symbol | Not yet certified for this candidate |
| Move / reorder code | Not yet certified for this candidate |
| Formatting only | Not yet certified for this candidate |
| Git file rename / move | Not yet certified for this candidate |
| Mixed move and edit | Not yet certified for this candidate |
| Invalid syntax / actionable error | Not yet certified for this candidate |
| Guardrail review | Not yet certified for this candidate |
Try it¶
Save the two source blocks as separate files with the shown extension, then compare them:
intentumdiff file before/code.as after/code.as
The installed Python wheel includes its parser components. The native CLI requires a component directory. Compare the result with the source change described above; agreement between APIs alone is not proof of correctness.