Resolved Bytes vtable

[aleksdmladenovic]

Description

I exposed the drop function of Bytes for resolving the memory fragmentation issues because Bytes are often very small (~50% of the data is less than 500 bytes). I invoked the drop function by using std::mem::drop().

#437

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Tests added/amended
• bazel test //... passes locally
• PR is contained in a single commit, using git amend see some docs

---

For testing, I added one test script for evicting items when there is not enough space.

Script: cargo test --test memory_store_test insert_drop_test -- --nocapture

Output:

• Printed Evicting item when the items should be evicted because there is no enough space.
• Printed BytesWrapper dropped and the Bytes data when the Bytes are dropped.

---

This change is 

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ aleksdmladenovic
❌ aleksandarmladenovic0330
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[allada]

This won't work for what we are trying to do. Hyper/Tonic/S3 takes a Bytes when sending http requests and we don't want to force a copy every time someone reads something. We need the drop to be called when Hyper/Tonic/S3 is done with it, not when we are done with it.

Reviewable status: 0 of 1 LGTMs obtained, and pending CI: Bazel Dev / ubuntu-22.04, Cargo Dev / macos-13, Cargo Dev / ubuntu-22.04, asan / ubuntu-22.04, docker-compose-compiles-nativelink (20.04), docker-compose-compiles-nativelink (22.04), license/cla, macos-13, ubuntu-20.04 / stable, ubuntu-22.04, ubuntu-22.04 / stable, windows-2022 / stable