Brezak
Brezak
I think you're underestimating how long the test will take. I've written some code that should just test the increment. ```rust use std::{hint::black_box, time::Instant}; fn next_if_some(num: u32, b: Option) ->...
This code won't handle vecs with zsts. One can construct a vector with usize::MAX elements today, like this: ```rust fn max_zst_vec() -> Vec { let mut data: Vec = Vec::new();...
> Maybe I'm stupid but if you have `usize::MAX` capacity the last element index is `usize::MAX-1`? You're not stupid. I was wrong.
Given #13279. Could we add a setup command to our CI tool that asks the contributor some questions and then setups the `config.toml` for them?
I'm sorry if the description isn't very coherent. It's **very** late here. I'm going to sleep. I'll fix everything tomorrow.
This is work for a future PR but several commands could be flags on other commands. For example both the test-check and cfg-check commands could be flags on the compile-check...
I'd like to pick this up.
If we're doing this one crate at a time a tracking issue to keep track which crates have been cleaned up would be useful.
I think this PR should be merged instead of #13203. The only thing this PR is (debatably) missing is logging the winit events we have skipped.
`bevy_mikktspace` is using the 2021 Rust edition. This makes it's minimum supported version Rust 1.56.0. The documentation will need to be updated.