| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2024-05-28 | Change Bytes::make_mut to impl From<Bytes> for BytesMut (closes #709) (#710)HEADmaster |  Anthony Ramine
| 4 | -52/+54 | |
| <Arc<T>>::make_mut returns a &mut T, such an API is doable for Bytes too and thus we should reserve Bytes::make_mut for that. Furthermore, it would be helpful to use From<Bytes> as a trait bound in some cases with other traits such as Hyper's body trait, where Hyper gives you Bytes values. Finally, making it impl From<Bytes> for BytesMut means the API is more easily discoverable as it appears on both Bytes and BytesMut. | |||||
| 2024-05-19 | Fix iter tests to use the actual bytes IntoIter instead of std (#707) |  Paolo Barbolini
| 1 | -4/+4 | |
| 2024-05-11 | Offset from (#705) |  Brad Dunbar
| 3 | -39/+20 | |
| 2024-05-05 | Add zero-copy make_mut (#695) |  Émile Fugulin
| 4 | -2/+341 | |
| 2024-05-05 | ci: silence unexpected-cfgs warnings due to `#[cfg(loom)]` (#703) |  Alice Ryhl
| 1 | -0/+1 | |
| 2024-04-26 | Tweak clear and truncate length modifications (#700) | Alice Ryhl
| 1 | -8/+6 | |
| 2024-04-25 | Improve BytesMut::split suggestion (#699) | Paolo Barbolini
| 1 | -1/+1 | |
| 2024-04-25 | Reuse capacity when possible in <BytesMut as Buf>::advance impl (#698) |  Paolo Barbolini
| 1 | -0/+8 | |
| 2024-04-24 | Bytes::split_off - check fast path first (#693) | Brad Dunbar
| 1 | -7/+7 | |
| Follow up to https://github.com/tokio-rs/bytes/pull/689 * If `at == self.len()`, we already know `at <= self.len()`. * If `at == 0`, we already know `at <= self.len()`. | |||||
| 2024-04-24 | Resize refactor (#696) | Brad Dunbar
| 1 | -9/+17 | |
| * use checked_sub * return when additional == 0 * move safe operation out of unsafe block * use spare_capacity_mut instead of chunk_mut We don't need to check capacity because it's already been reserved above. * Add safety comments * refactor to use guard clauses This would be better written with let-else, but we won't get that until `MSRV >= 1.65.x`. * use if-let instead of unwrap * reduce scope of unsafe blocks Co-authored-by: Alice Ryhl <aliceryhl@google.com> --------- Co-authored-by: Alice Ryhl <aliceryhl@google.com> | |||||
| 2024-04-17 | Truncate tweaks (#694) | Brad Dunbar
| 1 | -1/+2 | |
| 2024-04-11 | test(benches): encloses bytes into `test::black_box` for clone benches (#691) |  Joseph Perez
| 1 | -3/+3 | |
| Closes #690 Without it, it seems to me that compiler is able to inline the vtable, resulting in similar results for `clone_shared` and `clone_arg_vec`. | |||||
| 2024-04-10 | perf: improve Bytes::copy_to_bytes (#688) |  tison
| 1 | -7/+1 | |
| Signed-off-by: tison <wander4096@gmail.com> | |||||
| 2024-04-10 | Bytes::split_to - check fast path first (#689) | Brad Dunbar
| 1 | -7/+7 | |
| If `at == self.len()` then we already know `at <= self.len()`. If `at == 0`, it can't be greater than `self.len()`. | |||||
| 2024-04-09 | Don't set `len` in `BytesMut::reserve` (#682) | Brad Dunbar
| 1 | -2/+2 | |
| A fundamental invariant of `reserve` is that it can extend capacity while the stored data remains the same, even if it's moved to a new allocation. As a result, `len` can never change during a call to `reserve`. | |||||
| 2024-04-08 | Bytes: Use ManuallyDrop instead of mem::forget (#678) | Brad Dunbar
| 1 | -9/+11 | |
| 2024-03-22 | chore: prepare bytes v1.6.0 (#681)v1.6.0 | Brad Dunbar
| 2 | -1/+38 | |
| 2024-03-14 | Use ManuallyDrop instead of mem::forget (#675) | Brad Dunbar
| 1 | -14/+12 | |
| 2024-03-04 | Remove commented tests for Bytes::unsplit (#677) | Brad Dunbar
| 1 | -91/+0 | |
| Bytes doesn't have an unsplit method anymore. We can always retrieve these from git history if necessary. | |||||
| 2024-03-04 | Remove redundant reserve call (#674) | Brad Dunbar
| 2 | -2/+22 | |
| 2024-03-03 | copy_to_bytes: Add panic section to docs (#676) | Brad Dunbar
| 1 | -0/+4 | |
| Fixes #454. | |||||
| 2024-03-03 | Use Iterator from the prelude (#673) | Brad Dunbar
| 1 | -1/+1 | |
| CI is [failing][failure] due to unused_imports because Iterator is already in the prelude. Removing it fixes things up. [failure]: https://github.com/tokio-rs/bytes/actions/runs/8034858583/job/21946873895 | |||||
| 2024-02-23 | Refactor split_at/split_to (#663) | Brad Dunbar
| 1 | -26/+24 | |
| * set len a little more concisely * inline set_end * remove kind assertions * remove a duplicate assertion * remove redundant assertion and min * rename set_start to advance_unchecked | |||||
| 2024-02-06 | get_vec_pos: use &self instead of &mut self (#670) | Brad Dunbar
| 1 | -3/+3 | |
| I can't see any reason that get_vec_pos needs a &mut self. | |||||
| 2024-02-06 | set_vec_pos does not need a second parameter (#672) | Brad Dunbar
| 1 | -13/+11 | |
| The second argument to `set_vec_pos` always contains the value of `self.data`. Let's just use `self.data` and remove the second parameter altogether. | |||||
| 2024-02-06 | Calculate original capacity only if necessary (#666) | Brad Dunbar
| 1 | -6/+3 | |
| We don't need the original capacity if the shared data is unique, so let's not calculate it until after that check. | |||||
| 2024-02-06 | Use sub instead of offset (#668) | Brad Dunbar
| 1 | -2/+2 | |
| We're always subtracting here, and we already have a usize, so `sub` seems like a more appropriate usage to me. | |||||
| 2024-02-06 | Restore commented tests (#665) | Brad Dunbar
| 1 | -38/+41 | |
| These seem to have been commented by accident in #298, and are still passing. | |||||
| 2024-01-31 | refactor: make parameter mut in From<Vec> (#667) | Brad Dunbar
| 1 | -2/+1 | |
| Instead of re-declaring `vec`, we can just use a mut parameter. | |||||
| 2024-01-28 | Remove unreachable else branch (#661) | Brad Dunbar
| 1 | -3/+1 | |
| 2024-01-28 | Remove an unnecessary else branch (#662) | Brad Dunbar
| 1 | -2/+2 | |
| 2024-01-28 | Remove unnecessary namespace qualifier (#660) | Brad Dunbar
| 2 | -3/+3 | |
| 2024-01-19 | add `Bytes::is_unique` (#643) |  Cyborus04
| 3 | -0/+84 | |
| 2024-01-19 | BytesMut: Assert alignment of Shared (#652) | Brad Dunbar
| 1 | -0/+6 | |
| Back in #362, an assertion was added to ensure that the alignment of bytes::Shared is even so we can use the least significant bit as a flag. bytes_mut::Shared uses the same technique but has no such assertion so I've added one here. | |||||
| 2024-01-08 | Update CI config (#650) |  Taiki Endo
| 4 | -30/+33 | |
| 2024-01-08 | Update loom to 0.7 (#651) | Taiki Endo
| 1 | -1/+1 | |
| 2024-01-03 | readme: add security policy (#649) | Alice Ryhl
| 1 | -0/+9 | |
| 2023-12-28 | Use `self.` instead of `Self::` (#642) | Brad Dunbar
| 1 | -6/+6 | |
| I was a little confused about these calls using `Self::` instead of `self.` here. Is there a reason to use the former instead of the latter? | |||||
| 2023-12-28 | Simplify UninitSlice::as_uninit_slice_mut() logic (#644) |  Luca Bruno
| 1 | -1/+1 | |
| This reworks `UninitSlice::as_uninit_slice_mut()` using equivalent simpler logic. | |||||
| 2023-11-16 | docs: fix broken links (#639) |  Gabriel Goller
| 9 | -25/+9 | |
| Fixed a few broken links and converted a lot of them from the html-link to intra-doc links. | |||||
| 2023-10-19 | docs: typo fix (#637) |  DanielB
| 1 | -2/+2 | |
| Co-authored-by: Daniel Bauman <danielbauman@Daniels-MacBook-Pro.local> | |||||
| 2023-10-02 | Various cleanup (#635) | Alice Ryhl
| 8 | -137/+351 | |
| 2023-09-25 | docs: fix some spelling mistakes (#633) |  mxsm
| 2 | -2/+2 | |
| 2023-09-11 | Move comment to correct constant (#629) |  Lucas Kent
| 1 | -1/+1 | |
| 2023-09-07 | doc: fix changelog typo (#628) | Alice Ryhl
| 1 | -1/+1 | |
| 2023-09-07 | chore: prepare bytes v1.5.0 (#627)v1.5.0 | Alice Ryhl
| 2 | -1/+12 | |
| 2023-06-20 | Rename UninitSlice constructors for consistency with ReadBuf (#599) |  Michal Nazarewicz
| 2 | -24/+24 | |
| tokio::io::ReadBuf uses names `new` and `uninit` for its constructors. For consistency with that, rename recently introduced UninitSlice constructors to match those names. | |||||
| 2023-06-05 | Fix CI failure (#616) | Taiki Endo
| 2 | -0/+2 | |
| 2023-02-10 | Implement BufMut for `&mut [MaybeUninit<u8>]` (#597) | Michal Nazarewicz
| 2 | -13/+145 | |
| 2023-02-09 | Add a safe way to create UninitSlice from slices (#598) | Michal Nazarewicz
| 2 | -7/+51 | |
| Introduce UninitSlice::from_slice and UninitSlice::from_uninit_slice methods which safely create Uninit slice from provided slice of maybe uninitialised or initialised memory. In addition, add `From<&mut [T]>` implementations (for `T=u8` and `T=MaybeUninit<u8>`) which do conversion from slice to UninitSlice. Closes: #552 | |||||
 |
index : bytes | |
| Unnamed repository; edit this file 'description' to name the repository. |
| aboutsummaryrefslogtreecommitdiff |