diff options
| author | bogwi <bogwi@rakumail.jp> | 2025-05-05 22:39:03 +0900 |
|---|---|---|
| committer | bogwi <bogwi@rakumail.jp> | 2025-05-05 22:39:03 +0900 |
| commit | 3c0ba5bb55fe59ed1644c3e61fd2a81fb856624e (patch) | |
| tree | 039002fdf804a1eb5fd2428074ece74537f06b77 /src/types.cpp | |
| parent | af6b763449a7876f08b3edaf9875c57769f10bd4 (diff) | |
CHECK 4 done
The original errors:
1. `5024.odin(127:15) Error: Invalid use of a polymorphic type 'List($T)' in variable declaration`
2. `5024.odin(129:17) Error: Cannot determine polymorphic type from parameter: 'invalid type' to 'List($T)'`
Are gone. We now have a single, different error:
`5024.odin(124:28) Error: Unspecialized polymorphic types are not allowed in procedure parameters, got List($T)`
This error points directly to the `list : List($T)` parameter within the `List_Filter` procedure definition. This seems much more relevant to the actual problem (the interaction between the generic `List_Filter` and the concrete `default_filter`) than the original error about the variable declaration.
While this new error message might not be exactly pinpointing the default parameter issue, it correctly identifies the problematic procedure definition (`List_Filter`) as the source of the error, rather than the variable declaration (`my_list`). This seems like a step in the right direction for improving the error reporting for this kind of scenario.
Diffstat (limited to 'src/types.cpp')
0 files changed, 0 insertions, 0 deletions