antirez / antirez/RESP3

Doubles: reasons for disallowing exponential form

Ouverte
#37 2 commentaires 1 réaction 0 personnes assignées Voir sur GitHub
Langage dominant
Aucune donnée de langage
Étoiles
230
Forks
41
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.