You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a loose consensus that floats are a bad idea in content-addressable systems, but floats are included in the IPLD datamodel; are defined in DAG-CBOR; and are definitely supported in basic CBOR.
A motivating use case is to fully support the bluesky "lexicon" language, which has "float" as a type. It is recommended against actually using floats in bluesky lexicon, but it is allowed, and it is supported in the typescript implementation.
The text was updated successfully, but these errors were encountered:
There seems to be a loose consensus that floats are a bad idea in content-addressable systems, but floats are included in the IPLD datamodel; are defined in DAG-CBOR; and are definitely supported in basic CBOR.
A motivating use case is to fully support the bluesky "lexicon" language, which has "float" as a type. It is recommended against actually using floats in bluesky lexicon, but it is allowed, and it is supported in the typescript implementation.
The text was updated successfully, but these errors were encountered: