[racket-dev] bit-vectors and serialization

I'd call it an error if something couldn't be correctly serialized and 
deserialized between platforms.

Neil ⊥

On 12/16/2012 05:22 PM, Robby Findler wrote:
> If there's no significant performance penalty, then I'd say that we
> should make things work between 32bit and 64bit builds.
>
> (If there is a performance penalty then I'd still want to try to achieve
> that, at least.)
>
> Robby
>
>
> On Sun, Dec 16, 2012 at 6:18 PM, Ryan Culpepper <ryan at cs.utah.edu
> <mailto:ryan at cs.utah.edu>> wrote:
>
>     I'd like to make bit-vectors serializable so I can replace sql-bits
>     with them. I'll deprecate the current sql-bits names but keep them
>     around for a while.
>
>     The issue is that bit-vectors are implemented using fxvectors, which
>     are serializable, but simply serializing them will presumably cause
>     errors if a bit-vector is serialized on a 64-bit machine and
>     deserialized on a 32-bit machine or vice versa.
>
>     One solution would be to use bytes instead of fxvectors. The
>     performance is about the same as far as I could tell using the sieve
>     benchmark.
>
>     Another option is to declare that serialization across word sizes
>     doesn't work for bit vectors.
>
>     Any opinions?
>
>     Ryan
>     _________________________
>       Racket Developers list:
>     http://lists.racket-lang.org/__dev <http://lists.racket-lang.org/dev>
>
>
>
>
> _________________________
>    Racket Developers list:
>    http://lists.racket-lang.org/dev
>