Alphyr
Alphyr
`#[repr(transparent)]` guaranties that the type has the same layout that the inner one, so I think that the following examples should work : ```rust #[repr(tansparent)] #[derive(Zeroable, Pod)] struct TypedUsize(usize, PhantomData);...
Most types in `pyo3::types` have helper methods to create them easily (examples: [`PyString::new`](https://docs.rs/pyo3/latest/pyo3/types/struct.PyString.html#method.new), [`PyBool::new`](https://docs.rs/pyo3/latest/pyo3/types/struct.PyBool.html#method.new)). Is there a reason why there is no such method for `PyLong` and `PyInt` or is...
This is similar to [`OnceCell::get_or_try_init`](https://docs.rs/once_cell/latest/once_cell/sync/struct.OnceCell.html#method.get_or_try_init) and is very useful for fallible initialization.
When I try to parse types from this PDB from Microsoft, a get this error: `UnimplementedTypeKind(0xa)` The PDB: https://msdl.microsoft.com/download/symbols/combase.pdb/70E3ECDD8981C0FF8AC67BED63ABECF91/combase.pdb It does not seem to be documented in https://github.com/Microsoft/microsoft-pdb/ though.
It would be great if this crate was usable in a `#![no_std]` support, as `gimli`.
https://github.com/spacejam/rio/blob/319f7fb04014aa88540c3539bd97d5a0006a1eb9/src/io_uring/uring.rs#L733-L752 This code assumes that the layout of `std::net::SocketAddrV{4,6}` matches `libc::sockaddr`, but std makes no such promise. See rust-lang/rust#78802 for more details. Example fixes: tokio-rs/mio#1388, rust-lang/socket2#120.
I think `rand` is not exposed in the public API so this is not a breaking change.
I tried to read the following mp3 file: [silence.zip](https://github.com/RustAudio/rodio/files/7969043/silence.zip). With `rodio` 0.14 it works as expected but `rodio` 0.15 panics when calling `Decoder::new_mp3`. I used the following code to read...
It would be a great feature to have ! For the record, `goblin` already supports it: https://github.com/jan-auer/goblin/blob/master/src/pe/exception.rs
Currently, `::Error` is `()` so it cannot be converted to `Box`. Using `std::convert::Infallible` or a standalone type that implement `std::error::Error` would be more convenient.