-
Notifications
You must be signed in to change notification settings - Fork 39
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
Arrays? #202
Comments
Like many things, will! :P I have detailed plans for unboxed types, just haven’t finished implementing them, and sadly my most recent code is on a computer that’s out for repairs right now. :( White square brackets (ASCII My eventual goal is to specialise certain operations on certain types and sizes of array to enable simple vectorised code—for example, the Let me know if you have any further questions and I can offer usage examples—it’ll encourage me to use them as test cases. :) |
👍 I like. One question, is it odd that a boxed array is a linked list? Also, I like the idea of the instruction optimization based the size and type of the array. I've been thinking about the degree to which optimizations can be made by the compiler. For instance could it look at what functions are called on a generic"collection" and determine the best data type (array, linked list, or bst)? That seems plausible. Then I wondered if something similar could be done for boxed vs unboxed. Not so sure about that. |
I like the idea of having the compiler select an appropriate data structure based on usage patterns, like how some languages select different Auto-unboxing seems very possible—GHC does something like that to remove redundant box/unbox operations on small strict types like |
Can/will/does Kitten have a way to create arrays? ie Work with blocks of heap memory at a low level?
The text was updated successfully, but these errors were encountered: