This is, unfortunately, a breaking change, so I'm moving it to target the v2 branch.

The secondary solution (allow it to be escaped in parsing, but don't require it to be escaped in printing) appears to already be expected by the testsuite; see all_escapes.kdl and its expected output.

(I think superfluous escapes are fine - all it means is we can't give special meaning to an escaped forward slash \/ later - so I don't think we need to change any behavior here at all. But it would certainly be tidier to remove \/, since it does suggest that / would do something special in strings if not escaped.)

oh lol I should look at commit histories; that was changed by the OP several days ago. 👍

@tabatkins oh, sorry, i made a bunch of alternative fixes, one of which was to do exactly what you've suggested, which got merged 😝

If an alternate has been merged, can we close this?

The alternate that was merged was just a change to the expected serialization for the tests; the larger (breaking change) question of whether to remove the \/ escape entirely is still open as a possible 2.0 change.