tree f2bd76363af665ecb767d8894110d91e9fdd61e1
parent cf2a543085aaa479197f354a25e36a0e03dbd654
parent c5748994cab06d2e4d2b1b985bbbbc0eb396cb28
author bors[bot] <26634292+bors[bot]@users.noreply.github.com> 1593172170 +0000
committer GitHub <noreply@github.com> 1593172170 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJe9eDKCRBK7hj4Ov3rIwAAdHIIALF0+83sYBaRqLR/dq0Ih4xU
 jo1BCIDDcSV5U0IvWhWR1bdfl6Rg4BhyFtxgtSXdqHHbaijUTuHb+X1VU1GxoXAq
 WVkylVWyWLxgNvVVirVwGS4UKM+o9EccOHKG6F0k2MpPed9kcwhnnIynZ6r1tCCo
 a3rKjsrKY5/OoHtV5zSZwcp+YwW/2As2uBPpXShGie42+Gy1os7o8+iXoAIERBA8
 /daoM71YtUAPDUA9UykXf527rw/NhCa9wppfd2aV/5xQqz3o6yvSI5y+Uqn2KaBi
 QNNLSkeU0LmUSBajkPw5vPwK7ALksdaxHm6djXWPMeU8MLeVgZfqa9VOAsu8YLY=
 =iu3E
 -----END PGP SIGNATURE-----
 

Merge #205

205: Add a heap feature to libtock-rs/core. r=gendx a=gendx

This pull request adds a `heap` feature to the core crate of libtock-rs. This allows to configure the core crate to only enable and initialize the `HEAP` variable, while leaving the choice of defining a custom allocator.

Indeed, the `HEAP` is conveniently initialized in the entry point with the app's heap start/size.

An example use case is in OpenSK (see this pull request https://github.com/google/OpenSK/pull/123), where the custom allocator can print some debugging information about allocations & deallocation to the console - while the heap implementation is the same as the default of libtock-rs (i.e. `linked_list_allocator`).

---

An alternative to this feature could be to somehow communicate the app's heap start/size to the `main` function, so that each app can initialize its own allocator when the `alloc` feature is off.

Co-authored-by: Guillaume Endignoux <guillaumee@google.com>