Could use some more of these, especially for sequence and mapping :)

read_raw actually produces a JSON string that, because YAML is a superset of JSON, will parse fine. It doesn't return the original string as I don't know how to do it. I'll try the case @spalladino had, see if it can be parsed with a Union, and then I might add a few more specs before merging.

That's fine, I'd just like to make sure stuff like

foo: &foo
  - "foo"
  - false
bar:
  - foo: 1
    bar:
      <<: *foo 
  - "hello world\n\nyay"

is converted correctly :)

Nope, that doesn't work. I'll fix it to throw an error for the alias, those are not supported in the pull parser.

Well, not supported in mapping and also in read_raw.

Sad to hear but out of scope here. Take out the alias if you want, just wanted to show a more complex example ;)

I mean, the pull parser receives events, "mapping start" and "sequence start", it doesn't matter in what form you wrote the YAML. That's tested in the regular YAML pull parser specs.

It's not about parsing, it's that the correct string is serialized, since you do manual string building?

Yes, but those are the only cases to consider: string, array, hash. There's nothing else in the default YAML pull parser.

In any case, feel free to add a few more specs if you want :-)