| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| Back | FazBrowse Home | New Git URL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality🛠️ Refactor suggestion
Simplify double transmutation in new_ref_typed.
The method performs two unsafe transmutes in sequence, which is unnecessarily complex and increases the risk of errors. The conversion can be simplified.
impl<T> PyTuple<PyRef<T>> { pub fn new_ref_typed(elements: Vec<PyRef<T>>, ctx: &Context) -> PyRef<PyTuple<PyRef<T>>> { - // SAFETY: PyRef<T> has the same layout as PyObjectRef - unsafe { - let elements: Vec<PyObjectRef> = - std::mem::transmute::<Vec<PyRef<T>>, Vec<PyObjectRef>>(elements); - let tuple = PyTuple::<PyObjectRef>::new_ref(elements, ctx); - std::mem::transmute::<PyRef<PyTuple>, PyRef<PyTuple<PyRef<T>>>>(tuple) - } + if elements.is_empty() { + // SAFETY: Empty tuple conversion is always safe + unsafe { std::mem::transmute(ctx.empty_tuple.clone()) } + } else { + // SAFETY: PyRef<T> has the same layout as PyObjectRef + let elements: Box<[PyRef<T>]> = elements.into_boxed_slice(); + let elements: Box<[PyObjectRef]> = unsafe { + std::mem::transmute::<Box<[PyRef<T>]>, Box<[PyObjectRef]>>(elements) + }; + PyRef::new_ref( + PyTuple { elements }, + ctx.types.tuple_type.to_owned(), + None, + ) + } } }Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.