Changes
parent: tbd commit: 7ecfd36
Showing 1 changed file with 3 insertions and 3 deletions
giterated-stack/README.md
| @@ -13,9 +13,8 @@ A `GiteratedStack` is created by merging any number of `SubstackBuilder`s into t | ||
| 13 | 13 | `GiteratedStack` uses traits to embed reflection into the binary. `GiteratedStack` generates this reflection metadata at runtime from traits which are inherent on the types it is reflecting. |
| 14 | 14 | |
| 15 | 15 | This means that if, for example, `T: ValueMeta`: `T` also has an implementation of `T: IntoValueMeta`. |
| 16 | Giterated's Unifed Stack uses the `IntoValueMeta` implementation (generated by the compiler) to populate function pointers for reflection. We avoid an extra allocation over boxed `Fn*` traits. | |
| 17 | ||
| 18 | 16 | |
| 17 | * Giterated's Unifed Stack uses the `IntoValueMeta` implementation (generated by the compiler) to populate function pointers for reflection. We avoid an extra allocation over boxed `Fn*` traits. | |
| 19 | 18 | |
| 20 | 19 | * Reflection is used in Giterated to allow for deserializing objects and operations into their concrete type as soon as possible. |
| 21 | 20 | |
| @@ -38,4 +37,5 @@ The design of the Giterated Unified Stack is intended to create a data structure | ||
| 38 | 37 | |
| 39 | 38 | ## Implementation |
| 40 | 39 | |
| 41 | It is a goal for `giterated-stack` to be `#![no_std]` with `alloc`. This is to better facilitate integration through WASM support, support for more targets, and libraries that are more slim. | |
| 41 | \ No newline at end of file | |
| 40 | - It is crucial that the internals of Giterated's Unified Stack (reflection, etc) remain well-encapsulated and consumers do not have to concern themselves with the internals. | |
| 41 | - It is a goal for `giterated-stack` to be `#![no_std]` with `alloc`. This is to better facilitate integration through WASM support, support for more targets, and libraries that are more slim. | |
| 41 | \ No newline at end of file | |