Add chan_send_(int|double|buf), chan_recv_(int|double|buf).

[mattn]

Related issue #7

Sorry I'm not native specker. I may add mis-spelling or broken phrase. So I didn't write comment.

[mattn]

Best way maybe include chan_type in chan_t and validate with CHAN_TYPE_INT/CHAN_TYPE_DOUBLE/etc .

[tylertreat]

Can you explain what you mean by that?

[tylertreat]

Should probably check if wrapped == NULL just to be completely safe.

int* wrapped = malloc(sizeof(int));
if (!wrapped)
{
    return -1;
}

[mattn]

Can you explain what you mean by that?

go's chan is a typed as specified. chan string chan int. But this product doesn't handle type. So I'm thinking it need to check whether receiving type is a type sent.

[mattn]

Done

[tylertreat]

I'm not sure how you would implement typed channels. I think the typed
send/recv is a good solution. Do you have anything in mind?
On Sep 4, 2014 8:29 PM, "mattn" [email protected] wrote:

Can you explain what you mean by that?

go's chan is a typed as specified. chan string chan int. But this product
doesn't handle type. So I'm thinking it need to check whether receiving
type is a type sent.

—
Reply to this email directly or view it on GitHub
#8 (comment).

[mattn]

For example:

raw_chan = chan_init(0);

This chan doesn't check a type for sending type.

typed_chan = chan_init_with_type(0, CHAN_TYPE_INT)

This chan check a type for sending type.

[tylertreat]

I see what you mean. Enforcing the type might be important since if you have multiple producers sending different data types, you don't know how to receive them. Maybe chan_init should require a type?

typedef int chan_type;
#define CHAN_RAW 0
#define CHAN_INT 1
#define CHAN_DOUBLE 2
chan_t* chan_init(size_t capacity, chan_type type);

[mattn]

Maybe chan_init should require a type?

Yes, I'm thinking so.

[tylertreat]

I will merge this and the type checking can be added later.