I'm not sure that I am giving up on Emacs maintenance - the reference Noam supplied indicates this is a "well known" issue and somebody, has some intention, at some stage, to do something about it, but given the last update to referenced bug/email stream was 268 days ago, that intention may be on the back burner :-)
Faking up a code snippet is not necessarily that easy - and, again, the problem described in 29220 sounds exactly like the issue I am having. I have already supplied the GitHub reference to my package and indicated the file that contains the functions that use/invoke the read/print processes. This is a working package, so, in my opinion, that satisfies that request :-) Using the package is not difficult, it is fully documented with its own user manual and the writing/reading process of the Lisp Objects is completely transparent to the user and happens automatically the first time the minor mode is invoked i.e. any maintainer investigating the issue shouldn't need to spend too much time getting to a point where they can debug the issue. The file(s) are written to the "user-emacs-directory".