Two questions about representing types in Rune

[GavinRay97]

Hiya,

I was curious about the following:

• Is there a type for fixed-sized arrays in Rune? Something like array of 100 x uint32?
• What's the way to allocate buffers? Say if I want to allocate a memory arena/memory pool that lives for the duration of my application's lifetime

For example, the below works, but I have a feeling it's terribly inefficient:

fourKbArray = [0u32].resize(4096 * 1024)
// typeof(fourKbArray) = [u32], no static size info

%16 = call i32 @Sym1(i32 %15, %struct.runtime_array* @.str1), !dbg !121

Thank you =)

[GavinRay97]

The answer to Is there a type for fixed-sized arrays in Rune? is given here:

• Fixed-size array allocation and fixed-size types #37

[waywardgeek]

You are correct: Rune has no fixed-sized arrays... yet. This is an important feature for efficiency, and as a systems programming language, adding support for fixed-sized arrays should be in our TODO list. I added a 1-line comment about this in the TODO file. I think we can win most memory-intensive benchmarks without fixed-sized array support, which is why it isn't implemented yet.

DataDraw 1.0 and 2.0 had support for fixed-sized arrays, but for large applications in the electronics design autmoation space, we found little overall speed improvement for fixed-sized arrays, so support was never added to DataDraw 3.0.

[GavinRay97]

DataDraw 1.0 and 2.0 had support for fixed-sized arrays, but for large applications in the electronics design autmoation space, we found little overall speed improvement for fixed-sized arrays, so support was never added to DataDraw 3.0.

That is very interesting, thanks for sharing.

If you ever find yourself with the time, think it'd be kind of neat to read about some of the stuff you've discovered over the years in terms of performance while working on DD and the related, since some of it seems to go against conventional wisdom and there also seem to be some tricks in the DD repo I've not seen in other C codebases.