- Apr 07, 2018
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
And add a comment to why we need it. No other struct with a to_string() function is affected. https://github.com/sdroege/gstreamer-rs/issues/101
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Instead of StructureRef's to_string(), we were calling ToString::to_string() in the Display impl. Which then called into itself again. Fixes https://github.com/sdroege/gstreamer-rs/issues/101
-
-
- Mar 20, 2018
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Mar 19, 2018
-
-
There are different implementations and signatures for `get_pollfd` depending on whether the target platform is unix or windows. When generating the doc, we need both implementations to appear regardless of the target platform. This commit is inspired by the way Rust `std` library deals with `process::Command` OS dependent variants (https://doc.rust-lang.org/std/process/struct.Command.html#impl-CommandExt). Documentation can't be accurate though as we can't use the`std::os::windows` on `unix` and vice versa. As a workaround a fake fd class matching the other platform is declared. This could be further enhanced once `#[doc(cfg(...))]` is stabilized (https://github.com/rust-lang/rust/issues/43781) by declaring `#[doc(cfg(unix))]` or `#[doc(cfg(windows))]` instead of the hard coded comments `This is supported on **Windows/Unix** only`. Unfortunately, these comments disappear when generating will `--all-features` because they are not part of the documentation in the gir file.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
When feature `dox` is selected but not `futures`, the `futures` crate is not available as a dependency leading to a "can't find crate for `futures`" error.
-
- Mar 16, 2018
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
This should improve logging performance if the threshold is not high enough.
- Mar 14, 2018
-
-
Sebastian Dröge authored
-
- Mar 12, 2018
-
-
- Mar 07, 2018
-
-
Sebastian Dröge authored
-