Implicit Coercion to 64bit about blaze HOT 3 CLOSED

@ovillellas Ok, so the issue seems that blaze is ( unnecessarily ) trying to pass a carray object to a carray constructor and this is resulting in the implicit coercion.

>>> foo =  carray([ 1.,  2.,  3.], dtype=float32)
>>> print foo.dtype
float32
>>> bar = carray(foo)
>>> print bar.dtype
float64

This line in Blaze assumes Carray behavior == NumPy behavior which is resulting in the bug: https://github.com/ContinuumIO/blaze-core/blob/master/blaze/sources/chunked.py#L63

>>> foo = array([ 1.,  2.,  3.], dtype=float32)
>>> print foo.dtype
float32
>>> bar = array(foo)
array([ 1.,  2.,  3.], dtype=float32)
>>> print bar.dtype
float32

from blaze.

I think maybe the Issue #28 might be related to this.

from blaze.

Just a note: it is not only 32 to 64. All types seem to be promoted to their 64 bit equivalent.

int8->int64
float16->float64

complex gets promoted to complex128

complex64->complex128

btw, given that we support float16, wouldn't it make sense to support complex32? Just checked and it raises exception. But that seems to be numpy heritage.

from blaze.