- 21 6月, 2022 2 次提交
-
-
由 Mara Bos 提交于
-
由 Josh Triplett 提交于
-
- 20 6月, 2022 8 次提交
-
-
由 Yuki Okushi 提交于
Signed-off-by: NYuki Okushi <jtitor@2k36.org>
-
由 Chris Denton 提交于
-
由 Chris Denton 提交于
-
由 zhangyunhao 提交于
-
由 Mara Bos 提交于
-
由 nils 提交于
It's a map, not a vector.
-
由 Michael Goulet 提交于
-
由 Joshua Nelson 提交于
This is useful for combinators. I didn't add `clone` since you can already use `Clone::clone` in its place; copy has no such corresponding function.
-
- 19 6月, 2022 1 次提交
-
-
由 KaDiWa4 提交于
-
- 18 6月, 2022 9 次提交
-
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Nika Layzell 提交于
-
由 Ralf Jung 提交于
-
由 Paolo Barbolini 提交于
-
由 Paolo Barbolini 提交于
-
由 Paolo Barbolini 提交于
-
由 Aria Beingessner 提交于
This allows things like `Result<ExitCode, E>` to 'just work'
-
- 17 6月, 2022 5 次提交
-
-
由 Nika Layzell 提交于
-
由 Ralf Jung 提交于
-
由 Nika Layzell 提交于
This is an experimental patch to try to reduce the codegen complexity of TokenStream's FromIterator and Extend implementations for downstream crates, by moving the core logic into a helper type. This might help improve build performance of crates which depend on proc_macro as iterators are used less, and the compiler may take less time to do things like attempt specializations or other iterator optimizations. The change intentionally sacrifices some optimization opportunities, such as using the specializations for collecting iterators derived from Vec::into_iter() into Vec. This is one of the simpler potential approaches to reducing the amount of code generated in crates depending on proc_macro, so it seems worth trying before other more-involved changes.
-
由 Nika Layzell 提交于
This significantly reduces the cost of common interactions with TokenStream when running with the CrossThread execution strategy, by reducing the number of RPC calls required.
-
由 Nika Layzell 提交于
-
- 16 6月, 2022 6 次提交
-
-
由 Maybe Waffle 提交于
-
由 Maybe Waffle 提交于
-
由 pierwill 提交于
-
由 Xuanwo 提交于
Signed-off-by: NXuanwo <github@xuanwo.io>
-
由 Josh Stone 提交于
The important methods like `read` and `write` were already inlined, which can propagate all the way to inlining in user code, but these small state functions were left behind as normal calls. They should almost always be inlined as well, as they're just a few instructions.
-
由 Dan Gohman 提交于
-
- 15 6月, 2022 9 次提交
-
-
由 Dan Gohman 提交于
On Unix, describe these in terms of the underlying "file description". On Windows, describe them in terms of the underlying "object".
-
由 Dan Gohman 提交于
And `BorrowedHandle::try_clone_to_owned` and `BorrowedSocket::try_clone_to_owned` on Windows.
-
由 Dan Gohman 提交于
-
由 Frank Steffahn 提交于
-
由 KarlWithK 提交于
Incorrectly wrote "1" twice when writing test.
-
由 KarlWithK 提交于
Updated the btree's documentation to include two references to add_modify. The first is when the `Entry` API is mentioned at the beginning. With the same reasoning as HashMap's documentation, I thought it would best to keep `attack`, but show the `mana` example. The second is with the `entry` function that is used for the `Entry` API. The code example was a perfect use for `add_modify`, which is why it was changed to reflect that.
-
由 KarlWithK 提交于
Updated the HashMap's documentation to include two references to add_modify. The first is when the `Entry` API is mentioned at the beginning. I was hesitant to change the "attack" example (although I believe that it is perfect example of where `add_modify` should be used) because both uses work equally, but one is more idiomatic (`add_modify`). The second is with the `entry` function that is used for the `Entry` API. The code example was a perfect use for `add_modify`, which is why it was changed to reflect that.
-
由 Nika Layzell 提交于
-
由 Nika Layzell 提交于
-