You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, the typechecker is finally approaching the point of actual usefulness. I'm picking up 77 type errors in the dictionary, though I know at least some of those are definitely type checker issues. One I have verified is isBoolean\1. The final opcode is "l" when from context it should clearly be "c".
Most of the type errors I'm picking up are in the bst/rbt/t23 words. It looks like, from what I can see, the bst sealer code has a bug. raw.empty.bst produces a type with a sum inside a pair inside a pair, whereas the sealer expects a three-level deep pair structure. But these could just be type checker issues.
The text was updated successfully, but these errors were encountered:
The toBoolean\1 was definitely a type error. Thanks. :)
I wouldn't be surprised to find type errors in the bst/rbt/etc. code. That's the most complicated code in the dictionary at the moment. But I'm not seeing any problems with raw.empty.bst or empty.bst.
So, the typechecker is finally approaching the point of actual usefulness. I'm picking up 77 type errors in the dictionary, though I know at least some of those are definitely type checker issues. One I have verified is isBoolean\1. The final opcode is "l" when from context it should clearly be "c".
Most of the type errors I'm picking up are in the bst/rbt/t23 words. It looks like, from what I can see, the bst sealer code has a bug. raw.empty.bst produces a type with a sum inside a pair inside a pair, whereas the sealer expects a three-level deep pair structure. But these could just be type checker issues.
The text was updated successfully, but these errors were encountered: