In the latest update to Inko, defining a type automatically allocates it on the heap, granting flexibility in managing values. Borrowing incurs a borrow count, preventing premature drops and runtime panics. However, heap allocation has its costs, including potential optimization issues. New support for defining stack-allocated inline types introduces a unique aspect, allowing for easier handling and minimizing unexpected behavior. While inline types have limitations, they offer a more efficient alternative to heap types. Innovative solutions, such as compile-time borrow checking, are being explored to enhance memory safety and code performance. Overall, Inko continues to evolve with an eye towards efficiency and reliability.
https://yorickpeterse.com/articles/the-inevitability-of-the-borrow-checker/