Skip to content

Unexpected behavior when deserializing to double #434

@f-p-b

Description

@f-p-b

Deserializing to double using:

ryml::NodeRef node = tree["key"];
double value;
node >> value;

The following two cases behave unexpectedly:

  • When the key is followed by no value it gives a segmentation fault
  • When the key is a number with a letter in a position that is not the first it returns 0 instead of giving an error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions