The type of a range step, defined as Float32, changes to Float64

[simeonschaub]

I think I encountered something similar before. I believe that range internally uses double the precision in order to compensate loss of precision due to floating point error. Maybe in your case it might make sense to just collect this into an array or it might be better to try and use an integer range and scale it by a float.