Skip to content

Typecheck a literal dict key#264

Merged
mitchpaulus merged 3 commits into
mainfrom
typecheck-get-literal-key
Jul 1, 2026
Merged

Typecheck a literal dict key#264
mitchpaulus merged 3 commits into
mainfrom
typecheck-get-literal-key

Conversation

@mitchpaulus

Copy link
Copy Markdown
Owner

No description provided.

mitchpaulus and others added 3 commits July 1, 2026 09:44
Track a string literal's value as a `str` refinement (TKStrLit) so a
`get` with a statically known key resolves a shape field the same way the
`:name` getter does. `httpGet? "body" get?` now type-checks as `bytes`
instead of the union of every response field. Because the value rides the
stack as a type, it also resolves when the key reaches `get` through a
variable, not only when written inline.

The literal is a subtype of `str`: `unify` and every container
constructor widen it back to `TidStr`, so it behaves as `str` everywhere
else and never escapes into lists, dicts, shapes, unions, or match
subjects. Programs without string literals are unaffected; string-heavy
programs allocate less, since literal-key resolution avoids the
shape-to-union collapse the generic `get` path performs.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Exercises both the inline `"field" get?` and the variable-bound
`"field" k! ... @k get?` forms on a heterogeneous shape in the shared
success suite (type-checked and executed). Because the fields differ in
type, `count` must resolve to `int` specifically for `2 +` to type-check —
a dynamic key would type as `int | str` and be rejected — so the test
guards against a resolution regression.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mitchpaulus mitchpaulus merged commit fffa0de into main Jul 1, 2026
1 check passed
@mitchpaulus mitchpaulus deleted the typecheck-get-literal-key branch July 1, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant