In other words, in
a:="b"+"c"
IOW, does it implement the Slemiel's painting algorithm or not?
11–20 of 28 posts
In other words, in
a:="b"+"c"
IOW, does it implement the Slemiel's painting algorithm or not?
Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
type string struct {
data unsafe.Pointer
len int
}
The C version would be typedef struct string {
const *char data;
int len;
} string;
Edit: oh, ok. I Googled the "painting algorithm" reference. I swear I had read that before :-)Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
I can't imagine how you would even implement a string as anything other than a rune array.
Even a Pascal string is just the string length followed by characters.
Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
>Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? I can't imagine how you would even implement a string as anything other than a rune array. Even a Pascal string is just the string length followed by characters.
Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
>Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? I can't imagine how you would even implement a string as anything other than a rune array. Even a Pascal string is just the string length followed by characters.
You can also implement strings using a tree data structure. We do this in an implementation of Ruby that I work on because it can make concatenation faster.
Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
>Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? I can't imagine how you would even implement a string as anything other than a rune array. Even a Pascal string is just the string length followed by characters.
So, look at text editor data structures for other representations. Examples:
- https://en.wikipedia.org/wiki/Gap_buffer
Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
I'm not sure I 100% understand your question, but in Go a string is a two-word struct. type string struct { data unsafe.Pointer len int } The C version would be typedef struct string { const *char data; int len; } string; Edit: oh, ok. I Googled the "painting algorithm" reference. I swear I had read that before :-)
Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? In other words, in a:="b"+"c" IOW, does it implement the Slemiel's painting algorithm or not?
>Just curious, is a Go string a C string inside (rune array + nil) or a proper class array? I can't imagine how you would even implement a string as anything other than a rune array. Even a Pascal string is just the string length followed by characters.
Also not a Haskell programmer, and really not meaning to criticize. Haskell seems awesome and I should learn it some day.