robert
robert
Rc/Arc
Reference counted allocations could be very useful. This should be fairly simple to implement just by porting the standard library's implementations. Arc should only be allowed where the allocator is...
Using a constant could be finicky with block lifetimes, which is why I've opted to use a constructor for now. Since the `empty()` constructor always returns the same value, I...
this should lead to more highly-optimized code.
Having the ability to allocate singular values is nice, but for users to get optimal use of allocators, they will undoubtedly want to have at the very least a `Vec`,...
Sending allocators across thread boundaries is extremely useful. However, since most allocators are designed to have a reference to a parent allocator, `Send` for them requires that their parent is...
Crossbeam's CachePadded struct seems good for this.
There are a few invariants w/ regard to lifetimes which we should probably be testing are enforced.
Since we run jobs while busy-waiting for other jobs to be complete, panics in those jobs could leave those destructors in an incomplete state. While this is unlikely to affect...
Our current Proof-of-Validity (PoV) distribution system for backing is quite simple: A validator fetches a full PoV from a collator, the the validator announces the PoV, and other validators in...
Currently, the chain-selection subsystem only reverts a block B when one of its descendants B' issues a `Revert` log in its header targeting B. In practice, this happens when B'...