-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotreloading doesn't work with Complex stdlib module #114
Comments
The same is true for
|
I also seem to be getting the |
Interesting! I had no idea that OCaml wold forgo the OO runtime stuff if no objects were used. I'd recommend not using objects for now while I look into a fix :) |
@bsansouci yeah I switched it up and found an alternative way to encapsulate things. I'm pretty new to reasonml, and using objects was probably not the best approach anyways 😅 |
I wasn't gonna say it, but yeah, you'll get a lot of benefits from using records, functions and modules without the drawbacks of objects. Since you're new too, I think it'll be interesting for you to try these. They've substantially changed the way I code, leading to generally simpler and more robust code overall! |
I think OCaml/Reason is a great learning tool because it gives you those two options. I'm planning on making two versions of my game - one with objects and one with modules - and then seeing which one works better. |
Amazing effort, I'd love to hear how it's going and can offer help for how to shape your game in the functional way. Ping me on discord. |
Oh what's the Discord server for this sort of convo? |
Just writing this down so we remember to look into it one day. I have a project that uses the
Complex
module and the hotreloading is not liking it. When I runIndexHot
I get a:No idea why because
Complex
should be a module part of the stdlib... But maybe it has some dirty compiler hardcoded hacks to run faster and so you can't dynlink a module that uses ComplexThe text was updated successfully, but these errors were encountered: