Peter Jaszkowiak
Peter Jaszkowiak
Because of the way you've done the PR it's impossible to tell what changes you've made. If you can fix it to clean up the changes we might be able...
Where does this indicator appear? In the list of topics? There's already an indicator and the beginning and end of a topic.
We should have specific filters for everything, and then a base filter for everything: - parse.all (applied for everything) - parse.preview - parse.teaser - parse.post - parse.email
Fair enough, we should make the filter hooks all have very similar arguments etc so one doesn't need to write separate functions for each, then.
This is my understanding from the linked discussion. 1. Adding a `rust-toolchain` file would cause that toolchain to be installed on every `cargo` invocation, which takes time (usually unnecessarily) if...
Many of those commenting on the linked discussion are all top contributors and part of various Rust project teams, and they explicitly chose to not set a `rust-toolchain`. That said,...
Ideally these would just import from `libc` directly: ```rust // b.c use ::libc::printf; #[no_mangle] pub unsafe extern "C" fn funB(mut n: libc::c_int) -> libc::c_int { printf(b"funB\0" as *const u8 as...
Duplicate of #1050 ?
They essentially describe the same idea, the only difference is that this one suggests using `include!()` to implement it.
I've seen this apply to inline casts as well, where you end up with: ```rust ::core::mem::size_of::() as libc::c_ulong // or ::core::mem::size_of::() as libc::c_ulong as libc::c_ulonglong ``` Instead of ```rust ::core::mem::size_of::()...