feat(#5226): wire up-cased/low-cased to tt.as-ascii

[asmirnov-backend]

Closes #5226.

tt.as-ascii was added in #4752 as a standalone object that reads a single character as its ASCII numeric value (0-255), but it had no production callers.

This PR wires it in:

• tt.up-cased — removes the private nested [char] > ascii helper and calls tt.as-ascii instead.
• tt.low-cased — replaces the (up-cased text).ascii ... expressions with direct tt.as-ascii calls, computes distance locally, and drops the +alias tt.up-cased, fully removing the dependency on up-cased internals.

[github-actions]

🚀 Performance Analysis

All benchmarks are within the acceptable range. No critical degradation detected (threshold is 100%). Please refer to the detailed report for more information.

Click to see the detailed report

Test	Base Score	PR Score	Change	% Change	Unit	Mode
benchmarks.XmirBench.xmirToEO	11407.730	11685.006	277.276	2.43%	ms/op	Average Time

⚠️ Performance loss: benchmarks.XmirBench.xmirToEO is slower by 277.276 ms/op (2.43%)

[asmirnov-backend]

@yegor256, could you please take a look

[maxonfjvipon]

Thanks for wiring in tt.as-ascii. The up-cased half is solid, but the low-cased decoupling is incomplete and the description overstates what landed.

Looks good

• up-cased: the nested [char] > ascii is gone and every use (code, maxcode, mincode, and the as-ascii "A" inside distance) now goes through tt.as-ascii. The swap is behavior-preserving — the old helper padded to as-i64 (seven 00-) and as-ascii pads to as-i16 (one 00-), but both yield the same 0–255 value for a single byte.
• Keeping +unlint redundant-object is the right call. It guards the shared reduced / [accum byte] >> structure, not the removed helper — low-cased carries the same pragma and never had an ascii object, so dropping it would break the lint.

Needs a change

low-cased still depends on up-cased internals. Line 28 keeps:

code.plus (up-cased text).distance

and +alias tt.up-cased is still present, so a whole up-cased is instantiated just to read its inner distance. The dependency dropped from four reaches to one, not to zero — yet the description says this PR is "dropping the implicit dependency on up-cased internals", which isn't the case.

To actually close it, compute the distance locally and drop the alias:

minus. > distance
  as-ascii "a"
  as-ascii "A"

then code.plus distance, and remove +alias tt.up-cased.

Nit

as-ascii was introduced in #4752 (commit 5e0d031), not #5219.

[asmirnov-backend]

Thanks for the thorough review, @maxonfjvipon.

You're right that low-cased was still reaching into up-cased. Fixed in 6edb8dc:

• distance is now computed locally
• with code.plus distance, and +alias tt.up-cased is removed — so the dependency on up-cased internals is gone entirely now, not just reduced.
• Updated the PR description accordingly so it no longer overstates what landed.
• Also corrected the nit: as-ascii was introduced in sprintf Functionality Not Properly Utilized in EO #4752 (5e0d031), not feat(#4752): add tt.as-ascii object #5219.

[yegor256]

@maxonfjvipon take a look again please

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[0crat]

@maxonfjvipon Thanks for the review! You've earned +4 points for this: +12 as a basis; -8 for absolutely no comments posted; -4 for too few (30) hits-of-code; +4 to give you at least something. Your running score is +226; don't forget to check your Zerocracy account too).

[0crat]

@asmirnov-backend Thanks for the contribution! You've earned +12 points for this: +16 as a basis; -4 for too few (30) hits-of-code. Please, keep them coming. Your running score is +120; don't forget to check your Zerocracy account too).