Re: [igraph] degree sequence data type

[John Lapeyre]

> Historical reasons. Originally we only had an igraph_vector_t data type
> which was used both for integer and floating point vectors. Now we would
> have had to break the API if we wanted to switch to igraph_vector_long_t
> for those functions where it makes sense. Since most of the igraph users
> use it from a higher level language (R, Python or Ruby), these intricate
> details are completely invisible to them, and I personally think that
> the disadvantages of breaking the API at this point outweigh the
> benefits for the time being.

Ok, thanks. I suppose if it doesnt cause bugs its not a problem.
On my machine at least a double and long int are the same size.

--John