Remove usage of unsafeIO from getRayCollision functions about h-raylib HOT 6 CLOSED

Actually, I think the random number is because raycollision'hit uses CInt instead of CBool, so raycollision'hit returns garbage as the first 24 bits. #3 was a similar issue. That should be an easy fix. The main problem is that you have to print something for it to work properly. I think implementing the collision detection logic in Haskell is the best way to fix it.

from h-raylib.

Fixed, thank you for the quick fix and your hard work. Loving the bindings so far! Have a good one!

from h-raylib.

I will look into this. The functions should be okay for unsafePerformIO, but if it turns out they aren’t then I’ll implement collision detection math manually in Haskell. I would like to keep IO out of these pure functions.

from h-raylib.

It could be something else entirely, maybe I'm being suspicious of the wrong thing so feel free to correct me if I'm wrong! But this is the first time I've found something like this in Haskell so I'm a bit perplexed!

from h-raylib.

Are you sure that print is required? Maybe after changing CInt to CBool things will start working as you expect?

When you say moving the detection logic into Haskell, wouldn't that be essentially avoiding using Raylib? If that's the case then probably best to just flag it somehow so that people can write their own; I wouldn't say its the responsibility of your repo to re-implement things when it's just meant to be bindings.

from h-raylib.

I changed CInt to CBool in version 4.5.0.5. I tested it and it seems to be working fine with some example code. If this fixed the problem for you, you can close this issue.

from h-raylib.