-
Notifications
You must be signed in to change notification settings - Fork 352
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
tuple struct constructors and uninitialized fields #96
Conversation
#55 (run-pass) is now at
Associated constants are probably a big part of this, and 70 or more are threads
|
Nightly has the necessary changes now. |
I changed the PR base to solson:master since it contains all the code from the solson:always_encode_mir branch now due to #97. |
a7c712f
to
76ea018
Compare
I rebased over your changes (which enabled me to simply remove an entire hacky commit 🎉 ) I also re-enabled auxiliary tests for the host only (we need to make sure we drop a $someday, in the glorious future of lld or something else, we won't need such hacks |
…nZero optimizations
this is ready for review (and passing travis ^^) |
so... I did the minimal work for the i128 rustup. But one question is open: should we immediately change code to support 128 bit pointers, or is it ok to leave those at 64 bit? |
128 bit pointers are expected to never happen at this point. |
Great. So |
I'd keep only 64-bit immediate and load/store i128 from memory as needed. |
that's gonna make basic math really weird |
Also, there's no gain. |
Oh, that makes more sense, nevermind me. |
dd18c7c
to
bf51059
Compare
bf51059
to
8a6b823
Compare
tests now run on x86_64_unknown_linux_gnu, i686_unknown_linux_gnu, x86_64_pc_windows_gnu, x86_64_pc_windows_msvc |
Also update the travis script and the README to indicate that MSRV is 1.18 for builds, and 1.30 for development builds. Fixes rust-lang#96.
It might be easier to create a fourth variant to
Value
:Undefined
, but that wouldn't allow for fat pointers where one part isn't defined yet. Having an undefinedPrimval
might work.