This is intended to be a replacement/redesign for zerogc

Simplifies size calculation.

Use bumpalo for young-gen alloc

The oldgen collector is going to use a mimalloc heap
for its internal allocations.

Some strange errors with invalid Layout alignment (when using miri)

These address calculations can't really be avoided :/

This reverts commit 2f0926f95db863829159608e82bf7c5f4c98adf2

Allows using AddressSanitizer

Triggers errors earlier in AddressSanitizer

Because FFI is forbidden

This causes the to pass miri (onlt with tree borrows, not stacked borrows)

This emulates bumpalo::Bump behavior and avoids a slow HashMap

Unfortunately, miri still reports leaks

This adds some extra overhead in young-gen, but not much in old

…697c3ab'

git-subtree-dir: zerogc-nextv0.3
git-subtree-mainline: 3ff913b
git-subtree-split: 38a3b1e

In the v0.3 API, the context crate will no longer exist
and the simple crate needs to be rewritten.

The new version drops support for most features in v0.2

Will not be used with initial version of v0.3 API

Will be handled differently in v0.3 API

Doesn't delete any code right now

Reduces some features for derive macros (specifically warnings),
but is not really needed for the main crate.

Very unsafe

Remove unused dependencies.

Only offered with special extension trait `MutableKeys`.
Drop unused `deserialize` option for macro (GcDeserialize removed).

Drop unused dependencies.

The GcHeader api allows access to an object's internal header,
which contains the CollectorId.
For an array, the header also contains the length.

Implmentations can (and will) add extra metadata to their header
like mark bits and type info.

Make methods on Gc associated functions instead of methods
in order to avoid conflicts with the Deref trait.
This is what Arc and Box both do.

Currently doesn't compile