{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Rust 1.77 and 1.78: The Changes That Happened to u128/i128","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/9c002943\"></iframe>","width":"100%","height":180,"duration":633,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/rust-177-and-178-the-changes-that-happened-to-u128i128.\n             Rust has long had an inconsistency with C regarding the alignment of 128-bit integers on the x86-32 and x86-64 architectures.  \n            Check more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #rust, #rustlang, #rust-changes, #rust-1.77, #rust-1.78, #rust-u128, #rust-update, #rust-incorrect-alignment,  and more.\n            \n            \n            This story was written by: @Rust. Learn more about this writer by checking @Rust's about page,\n            and for more stories, please visit hackernoon.com.\n            \n                \n                \n                Rust has long had an inconsistency with C regarding the alignment of 128-bit integers. This problem has recently been resolved, but the fix comes with some effects that are worth being aware of. As a user, you most likely do not need to worry about these changes unless you are. Ignoring the `improper_ctypes*` lints and using these types in FFI.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}