sefer-alloc 0.2.1

A safe-by-construction, 100% Rust memory toolkit (no C/C++ libraries — no libnuma/mimalloc/jemalloc/snmalloc/tcmalloc): a single-threaded handle store (Region<T>) and a drop-in #[global_allocator] (SeferAlloc) over one verified segment substrate, with #![forbid(unsafe_code)] at the top.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

---
name: Feature request
about: Propose a new capability or API for sefer-alloc
title: "[FEATURE] "
labels: enhancement
assignees: ''
---

## Use case

<!-- Describe the concrete problem or scenario this feature addresses.
     "I want X" is less useful than "When doing Y, I cannot achieve Z because..." -->


## Proposed API

<!-- If you have a specific public API in mind, sketch it here. Otherwise leave
     blank. -->

```rust
// proposed signatures / types / trait impls
```


## Alternatives considered

<!-- What workarounds exist today? Why are they insufficient? -->


## Safety and verification impact

<!-- sefer-alloc is a verification-first project. Please answer: -->

- Will this feature require adding `unsafe` code?
  - [ ] No
  - [ ] Yes — in which module(s)?

- Which verification layers will need new coverage?
  - [ ] `cargo test` (unit / integration)
  - [ ] `proptest` differential
  - [ ] `miri`
  - [ ] `loom` model check
  - [ ] ThreadSanitizer
  - [ ] `cargo fuzz`
  - [ ] Cross-arch (aarch64 weak-memory smoke)
  - [ ] None / unclear

<!-- Any concern about performance impact? Should a bench be added? -->


## Additional context

<!-- References, prior art in other allocators, links to related issues, etc. -->