Suggestion: use 2D arrays instead of vectors about bindings-portaudio

[ChristopherKing42]

For the array suggestion, you could even make the channel index polymorphic. That is, instead of (Int, Int), it would be Ix i => (Int, i). The user could still make i be Int, but they could also use something like data Channel = Left | Right or what not. The functions needed to convert arrays to pointers do not care what index you use as long as it is Ix.

[fumieval]

I'm not a big fan of using Arrays or lists; there's a deliberate design choice of using a storable vector of static length data (e.g. V2), because it doesn't make sense to have dynamically changing number of channels in a stream. It also helps to have cache-friendly efficient operations.

[ChristopherKing42]

Storable Arrays can not change length in any dimension. Also, the current library does not guarantee static length, since Foldables can have a length that is different than the number of items they physically contain, perhaps in a variable way. For example, you can have data Foo a = Foo Int a, with toList (Foo n a) = replicate n a.

[ChristopherKing42]

If you want the length to be encoded in the type, you could use arrays where the bounds for the channel are (minBound, maxBound), or use fixed-vector which provides this typeclass specifically for fixed length vector types.

[fumieval]

I don't want 2D arrays because of the lack of API and you'll have to write elements one by one, for each channel. Fixed length vectors from the linear package are intended ones right now.

[ChristopherKing42]

Okay, I think I understand why the library is the way it is now. I'll just close this issue.