RayPals/Claro
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

test: cover chained object field aliases

Browse Source
This commit is contained in:
Hermes Agent
2026-09-06 14:06:26 +00:00
parent 1f5b5387b0
commit 9b93bea7e0
7 changed files with 40 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ADVANCED_STATIC_TYPING.md
+17 -1
View File
@@ -74,7 +74,7 @@ Type mismatch for field alias.score: expected NUMBER, but this value looks like
This is intentionally limited to simple aliases. Broader object-flow analysis through branches, loops, and complex expressions remains planned.
`CHECK TYPE` also follows this simple alias for direct field metadata checks:
`CHECK TYPE` also follows simple aliases for direct field metadata checks. This includes a second alias, so learners can give an object a more descriptive local name without losing the class field information:
```claro
NEW Player player
@@ -83,12 +83,28 @@ SET alias.score 10
CHECK TYPE alias.score IS NUMBER
```
```claro
SET backup alias
CHECK TYPE backup.score IS NUMBER
```
If the requested type is wrong, the diagnostic names the alias and the declared field type:
```text
Type check failed: expected TEXT, but alias.score looks like NUMBER.
```
The same diagnostic remains specific after the second alias:
```claro
SET backup alias
CHECK TYPE backup.score IS TEXT
```
```text
Type check failed: expected TEXT, but backup.score looks like NUMBER.
```
## Function parameter checks
Claro now has a small static-checking foundation for function arguments. Keep the beginner-friendly function syntax, then put the expected type inside the function with `CHECK TYPE`: