- Aug 20, 2020
-
-
Josh Triplett authored
Let's prevent this from happening again.
-
- Sep 12, 2019
-
-
gnzlbg authored
-
- Jun 27, 2019
-
-
Adam C. Foltzer authored
-
- Mar 27, 2019
-
-
Alex Crichton authored
-
- Nov 20, 2018
-
-
gnzlbg authored
-
- Oct 30, 2018
-
-
Jonathan A. Kollasch authored
-
- Apr 10, 2018
-
-
Mike Hommey authored
`pthread_mutex_t` varies across architectures, in several ways: - endianness alters the ordering of bytes, since the contents of the struct are larger than 8-bit. - its length varies. - the location of the mutex kind (`PTHREAD_MUTEX_RECURSIVE`, `PTHREAD_MUTEX_ERRORCHECK` or `PTHREAD_MUTEX_ADAPTIVE_NP`) varies between 32-bit and 64-bit: On 32-bit architectures, it is preceded by three int/unsigned int, while on 64-bit architectures, it is preceded by four of them. These initializers are only available from <pthread.h> when _GNU_SOURCE is defined. Relax the cfg_if check in ci/style.rs to allow #[cfg(target_endian)] tests.
-
- Mar 02, 2016
-
-
Alex Crichton authored
It's tough to have PRs bounce or to have a back and forth with contributors about minor style quibbles. Sometimes it ends up just being easier to fix style after the fact, but let's add some automation to help this! This commit adds a script to run on CI and locally to verify the style of this repository. There's a few stylistic guidelines to ensure that definitions are understandable across the jungle of modules. This consistency should help assist readability for any future readers!
-