Why is the FloatingPoint trait private?

[dchammond]

I am trying to write a generic library on top of arrayfire-rust. For most Array::* functions, having T: arrayfire::HasAfEnum is enough but for functions like arrayfire::dot, that has the additional bound of FloatingPoint, I cannot write a wrapping function since that trait is implemented in utils but utils is a private module.

Is there a reason this is the case?

[9prady9]

I haven't exposed some traits that were merely acting as input Array type restrictions to discourage implementations of these traits for user defined types. But, you are correct about the cases where these traits need to be public to write a generic function that accepts required Arrays.

I haven't figured out how to best handle both the above mentioned situations, hence kept them private at the moment. I will look into it and have the fix ready for next crate release.

[9prady9]

@dchammond I have fixed this in #188 can you please test the changes and let me know if that fixed the problem for you. Thank you.