Repository navigation
feat(renamer): shadow token 中段裁定——段外花括号 fail-loud - #111
Merged
Merged
Conversation
luiox
force-pushed
the
feat/shadow-descriptor-slot
branch
from
October 30, 2026 01:54
8d0f72a to
4d7dcc6
Compare
§4 落地:${ 出现在类型名/操作数中段(非段首)不展开、不静默——二进制
名文法不含花括号,未标记的引用形状混入裸名属调用方笔误。Descriptor 槽
类型段与 JasmBody 裸引用部(含 owner/name 分段后逐段裁定,段首 ${
句柄路径不受影响)→ malformed-handle 带 $$ 转义指引;$${ 显式转义
两槽均保留字面。name 槽维持整串二选一不引入中段扫描:Raw 恒等回显
(verifyRaw=false 直通位)或核表 raw-not-found 响亮,零漂移不变。
4d7dcc6 提交信息声称 0.3.3 接线,但根 xmake.lua 的 add_requires 版本钉 未随之升级,仍解析 0.3.2:孤立代理反汇编回归 3 例在 main CI 与本地全量 里失败。补钉后 delete-then-rebuild 重建门全量 1903 例 0 失败。
矩阵钉住中段 guard 与合法嵌套形态的边界:raw owner + 嵌套成员句柄
(方法/字段 × 带/不带描述符)、句柄 owner 复合、描述符多类型段/数组段
内嵌句柄、shadow 显示复合名零漂移直通——全部正常展开或直通。
owner 段内含 '.' 的复合名(显示形 owner + 嵌套句柄):JasmBody 槽契约
OWNER = 裸内部名('/' 分包),按首个 '.' 分段后嵌套句柄落于 name 段
中段,中段 guard fail-loud;即使改在 .${ 边界分段,dotted owner 与
表内句柄 owner 也不自洽,同为响亮报错。钉住现行语义(消息带 $$ 转义
指引),不改 guard 顺序。
luiox
force-pushed
the
feat/shadow-midstring-guard
branch
from
October 30, 2026 02:52
5a2d9d5 to
d0083df
Compare
Owner
Author
|
rebase + 两项收尾(原 5a2d9d5 → d0083df,重放在 4d7dcc6 之上):
本地 delete-then-rebuild 重建门全量 1903 例 0 失败(main 基线 1898 + 孤立代理 3 例随 0.3.3 转绿 + 新钉扎 2 例)。 |
libjhasm 0.3.3(e4fb91f)自带内联 libjbc 定义最高到 0.4.22(其自身 钉定版),包沙箱按内联定义解析后端依赖;顶层 0.4.23 被合并进沙箱需求 后在内联定义中查无版本映射,xmake 以版本号作 git ref 直取 libjbc 仓 ——远端无该 ref,Configure 期确定性失败(双平台)。回落 0.4.22 并对 libjhasm.libjbc 嵌套 dep 加显式 requireconf 钉定,保持全消费图单实例。 0.4.23 为上游仓库清理/测试收编批,消费面无功能差异。 清空本地全局包库 libjbc/libjhasm 强制从源解析(与 CI 干净机同路径) 两包 install ok;delete-then-rebuild 重建门全量 1903 例 0 失败。
Owner
Author
|
补:上条 push 后 CI 双平台确定性挂在 Configure( |
This was referenced Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
内容
堆叠于 #110。规范 §4:
${出现在类型名/操作数中段(非段首)不展开、不静默——二进制名文法不含花括号,未标记的引用形状混入裸名属调用方笔误。L…;类型段内容含花括号(且非段首${)→ malformed-handle,消息带$${转义指引;.分段后逐段裁定——段首${句柄路径不受影响,段外花括号 → malformed-handle;测试
新增 3 组:Descriptor 中段/孤立花括号/转义保留、name 槽零漂移与核表响亮、JasmBody 中段与转义。shadow token 42 组全绿;全仓 1895 通过(3 posix-skip)。