From: Wouter van Oortmerssen Date: Mon, 26 Aug 2019 21:59:21 +0000 (-0700) Subject: Clarified value reuse in FlexBuffers X-Git-Tag: v1.12.0~153 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=bd31dd2425fecc5d0b10f3bf4be8c84635fb63ba;p=platform%2Fupstream%2Fflatbuffers.git Clarified value reuse in FlexBuffers Change-Id: Ib771bfa46ccdf38eff25be857b1b73f8b300c649 --- diff --git a/docs/source/FlexBuffers.md b/docs/source/FlexBuffers.md index a089df3..f481cba 100644 --- a/docs/source/FlexBuffers.md +++ b/docs/source/FlexBuffers.md @@ -98,10 +98,10 @@ allows a single type, and uses a bit less memory. `IndirectFloat` is an interesting feature that allows you to store values by offset rather than inline. Though that doesn't make any visible change to the user, the consequence is that large values (especially doubles or -64 bit ints) that occur more than once can be shared. Another use case is -inside of vectors, where the largest element makes up the size of all elements -(e.g. a single double forces all elements to 64bit), so storing a lot of small -integers together with a double is more efficient if the double is indirect. +64 bit ints) that occur more than once can be shared (see ReuseValue). +Another use case is inside of vectors, where the largest element makes +up the size of all elements (e.g. a single double forces all elements to +64bit), so storing a lot of small integers together with a double is more efficient if the double is indirect. Accessing it: