-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for Cognate words?? #19
Comments
i can try to help with documentation, if only the admins will want to |
I'm currently at university so I'm a tad busy, but I'll be able to write some more documentation once the term finishes - as well as actually finish the compiler rewrite! |
Also, the behaviour of some combinators such as |
I might use the "old" (i.e. current) behavior of |
Well that part of the behavior I'm keeping. The bit I'm concerned about is the fact that you can do this, maxing blocks and value types.
The problem with this being that it has to do dynamic dispatch on the type passed to it, and it's very difficult to generate good code from this. |
Well that part of the behavior I'm keeping. The but I'm concerned about is the fact that you can do this, maxing blocks and value types.
The problem with this being that it has to do dynamic dispatch on the type passed to it, and it's very difficult to generate good code from this. Perhaps a better solution would be to have variants of |
This is uglier but generates much better code, since types are more deterministic:
|
Unfortunately I can't find any other languages that implement anything like the |
There isn't any documentation on each builtin word, and so for the ones that take and/or return blocks, the semantics are very confusing.
Case
in particular. What are the semantics of that, and everything else? Writing it as Forth stack-effect diagrams or just some example code would help.The text was updated successfully, but these errors were encountered: