-
Notifications
You must be signed in to change notification settings - Fork 748
check empty layout when padding bytes #494
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
Conversation
@bors-servo r+
|
📌 Commit df2ff4f has been approved by |
check empty layout when padding bytes fast workaround to fix issue #493 need to investigate why layout is empty
I need investigate it more deep to find out why it cause an empty layout, then I will add the test case |
☀️ Test successful - status-travis |
I'm afraid nothing has changed with this PR:
|
@dignifiedquire please try PR #495 |
@flier, better with the patch, no more division errors but now these fun errors https://gist.github.com/dignifiedquire/68f882ff94d63e195dbda124944d9d00 I have installed llvm, gtk+ (for the glib headers) and openssl via homebrew (which are the ones I am referecing in build.rs) Details about how I built librtcdcpp can be found here: chadnickbok/librtcdcpp#2 |
Thanks for digging into it @flier! Sorry for not being so much on top of this, but I had classes + work to do today :/ @dignifiedquire: I believe those other issues are known(-ish) issues about how partial template specialization is handled (hint: Is hard due to how libclang gives us that info, and we can't handle it all on rust anyway). The way to make that work is marking as opaque the types that get wrong layout/template params for now. |
Great, I will try this out later today and report back. Thank you both for the super fast help! |
Don't thank me, thank @flier who did pretty much all the digging here! |
you are welcome :) |
fast workaround to fix issue #493
need to investigate why layout is empty