Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Mar 24, 2020

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Mar 24, 2020
TimHambourger and others added 7 commits March 25, 2020 12:30
macOS-10.13 has been removed.
This fixes `cargo test --no-default-features`.
When `serde` is used, it would enable its default feature `std`.
This of course breaks no_std build.

Fix this by disabling serde's default features. This should work for
both serde + std and serde + no_std case.
* Format with rustfmt

* Add rustfmt check to CI
@pull pull bot added the merge-conflict Resolve conflicts manually label May 22, 2020
taiki-e and others added 20 commits May 24, 2020 06:30
Remove a remark from the doc that pertained to the inline
layout and is no longer true.
--no-self-update is necessary because the windows environment cannot
self-update rustup.exe.
There are issues with regard to uninitialized memory. We are avoiding
stabilizing this function for now.
Users of `BufMut` are unable to defend against incorrect implementations
of `BufMut`, this makes the trait unsafe to implement.

Fixes #329
The previous description focussed a lot on the `Arc` based implementation
of `Bytes`. Given the vtable based implemetation, this is however not the
only valid implementation. This changes the description a bit in order
to de-emaphasize the `Arc` part, and to describe that other implementations
are possible.

This should also be necessary if the vtable gets public.
paolobarbolini and others added 30 commits January 9, 2025 17:13
Co-authored-by: Alice Ryhl <aliceryhl@google.com>
Co-authored-by: Michal 'vorner' Vaner <vorner@vorner.cz>
Signed-off-by: discord9 <discord9@163.com>
During a dependency review we noticed that the bytes crate includes various development scripts. These development scripts shouldn't be there as they might, at some point become problematic. As of now they prevent any downstream user from enabling the `[bans.build.interpreted]` option of cargo deny.

I opted for using an explicit include list instead of an exclude list to prevent these files from being included in the published packages to make sure that everything that's included is an conscious choice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.