antirez / antirez/RESP3

Doubles: reasons for disallowing exponential form

未关闭
#37 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
没有语言数据
星标
230
派生
41
PR 合并指标
30 天内没有已合并 PR

描述

The specification indicates, for doubles:

> Exponential format is invalid.

However, this means that very large and very small values are now very verbose on the wire; additionally, many frameworks make *not* using E format challenging. This is also contrary to previous redis handling, which allows E formats, for example in the `INCRBYFLOAT` documentation there exists the sample:

``` txt
INCRBYFLOAT mykey 2.0e2
```

For example, IEEE754's max/min values would be over 300 bytes, to transmit a theoretically 8 byte payload.

I'd like to challenge whether this is a good idea, preferring to allow exponential form when appropriate. It is also notable that some platforms make it actively hard to *not* use E form.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。