Why Use Unfriendly &&char?

[Wajinn]

The use of &&char for the public functions in vlang's raylib and raygui bindings looks unfriendly and perplexing. Other bindings, for their public functions, use the equivalent of []string. Which makes more sense.

For the example below, text arguably should be an array of string ([]string). The count parameter next to it, would be the array.len, for what's in the array.

pub fn gui_list_view_ex(bounds Rectangle, text &&char, count int, scroll_index &int, active &int, focus &int) int

And even more interesting, V's documentation doesn't elaborate on &&char usage, other than its a kind of interoperability type.

[Wajinn]

A viable vlang solution, for the function above, is to use below:

array := [c"hello", c"world"] and then cast it &&char(array.data).

array's type is []&u8

In this way, array.len can be used for the count parameter as well (for the above function).

As function:

fn strchar(arr []string) &&char {
	mut barr := []&u8{} 
	for ele in arr { 
		barr << ele.str 
	}
	return &&char(barr.data)
}