heapless

heapless copied to clipboard

Remove implementing Deref<Target = [T]> for HistoryBuf

3

There is already `as_slice()` which gives access to the underlying backing array where the elements are not in the order of writing. With automatic dereferencing, functions like `iter()` or `windows()`...

sirhcel

Streamline HistoryBuf interface

1

An addendum to #610 for streamlining the interface of `HistoryBuf` even further. I'm opening this PR with two proposals for starting a discussion.

sirhcel

Performance regression for `HistoryBuf(fer)::write()` with heapless 0.9.1

3

## Description I've been using heapless's `HistoryBuffer` (now renamed to `HistoryBuf`) as a sliding search window with much success. More precisely, I have an iterator over a substantial number of...

BVollmerhaus

- [ ] https://github.com/rust-embedded/heapless/pull/610 - [ ] https://github.com/rust-embedded/heapless/pull/611

sgued

### Problem The `heapless` crate currently lacks a Binary Search Tree (BST) implementation. BSTs are essential for use cases like implementing process schedulers with priorities in kernel environments, where efficient...

stevefan1999-personal

Possible UB in the `pool::UnionNode<T>` and `pool::Node` types

6

As part of #562 I am working through the usage of `unsafe` code and I think I uncovered some UB in the `pool` module that affects `Arc` and `Box`. I...

Mortano

Build error when compiling with `esp-idf`

7

I get this error: ```sh error[E0223]: ambiguous associated type --> /home/esp/.cargo/registry/src/index.crates.io-6f17d22bba15001f/heapless-0.9.1/src/c_string.rs:181:17 | 181 | Err(FromBytesWithNulError::InteriorNul { position }) => { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | help: if there were a trait named...

SeaRoll

tests: add `Vec` + `String` fuzz harnesses

6

Adds a basic fuzzing test harness using `cargo-fuzz` to run randomized tests against the `Vec` and `String` types.

0xllx0

Allow setting visibility of the pool struct in the `box_pool!` macro

2

While I think this is a good change, unfortunately it's a breaking change and hence keeping it in draft for now until the next API break (perhaps 1.0).

zeenix

`IndexSet` depends on the `View` type for `IndexMap` being available. `IndexMap` is currently implemented with a `CoreMap`type that looks like: ```rust struct CoreMap { entries: Vec, indices: [Option; N], }...

sgued