Daily Thought - 2024-10-19
Hey, I'm Hanno! These are my daily thoughts on Crosscut, the programming language I'm creating. If you have any questions, comments, or feedback, please get in touch!
This thought was published before Crosscut was called Crosscut! If it refers to "Caterpillar", that is the old name, just so you know.
On the topic of memory allocation, there's an interesting perspective I came across recently: That memory allocation should be async. Meaning that the memory allocation API should not necessarily return an error, if enough memory isn't available right now; but a future or promise that resolves to allocated memory, once that becomes available.
James Munns presented this on the Self-Directed Research Podcast. That idea makes a lot of sense to me. And while nothing is set in stone regarding concurrency in Caterpillar, the same async/await style that Rust uses seems like a good fit. Maybe this approach to memory allocation will be a good fit too!
Hey, you! Want to subscribe to my daily thoughts? Just let me know (maybe include a nice message, if you're up for it), and I'll send you an email whenever I post a new one.