Skip to content

Conversation

@jramapuram
Copy link
Member

  • add a param for the lib directory
  • fix a bug that will arise when you upgrade to rust 1.3

@9prady9 9prady9 self-assigned this Jul 20, 2015
9prady9 added a commit that referenced this pull request Jul 20, 2015
@9prady9 9prady9 merged commit 982ebdf into arrayfire:master Jul 20, 2015
@pavanky
Copy link
Member

pavanky commented Jul 20, 2015

Why is it not complaining for the regular integer types?

@jramapuram
Copy link
Member Author

Because integers can be upcast.
Bools are not 0/1 like in cpp.

@jramapuram
Copy link
Member Author

Ah no I misunderstood.
I guess they are allowable to be cast to ints but not floats? Not sure. Will have to dig into rust spec

@9prady9
Copy link
Member

9prady9 commented Jul 20, 2015

Hm, i just checked this and it worked fine in the example.

let test: bool = false;
println!("{} , {}, {}", test, test as i32, test as f64);

however, i am still doubtful about pointer type

@jramapuram
Copy link
Member Author

Do you have rust 1.3?

@9prady9
Copy link
Member

9prady9 commented Jul 20, 2015

nope, i have 1.1. Are you using nightly ?

@jramapuram
Copy link
Member Author

Yes. I'm guessing this will pop up soon in the release builds. This way should be prepped for both cases.

@jramapuram jramapuram deleted the hotfix/build branch February 15, 2016 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants