From @zoffixznet

The newest JSON spec—contrary to previous versions—does allow non-object/array things at the top level. Reference​: http://rfc7159.net/rfc7159#rfc.section.2 (second paragraph, especially).

Rakudo's from-json built-in, however, displays an error when attempting to decode JSON conforming to this newest spec​:

<Zoffix> m​: say from-json "42"
<camelia> rakudo-moar 5ed58f​: OUTPUT«Invalid JSON​: 42␤ in block <unit> at /tmp/r522Mw8UZf line 1␤␤»
<Zoffix> m​: say from-json "false"
<camelia> rakudo-moar 5ed58f​: OUTPUT«Invalid JSON​: false␤ in block <unit> at /tmp/eCGN9CXVDB line 1␤␤»
<Zoffix> m​: say from-json '"42"'
<camelia> rakudo-moar 5ed58f​: OUTPUT«Invalid JSON​: "42"␤ in block <unit> at /tmp/kfesR2DMMW line 1␤␤»

From @zoffixznet

Made a PR fixing this​: rakudo/rakudo#687

From @coke

On Thu Jan 21 08​:34​:04 2016, cpan@​zoffix.com wrote​:

Made a PR fixing this​: rakudo/rakudo#687

There's a competing request to hide from-json and to-json (though I cannot find the discussion now).

If we hide the functions so they are only available to rakudo internals, then we don't need to worry about this.

--
Will "Coke" Coleda

From @zoffixznet

The functions in question are now internal, so the RFC is irrelevant. Closing.

@zoffixznet - Status changed from 'new' to 'rejected'