Pre-submission discussion: code walking

[Michael Raskin]

                Hello.
        I want to try to do something about portability of universally
present features, given that stndard revisions are extremely unlikely,
and CDR process seems to be the best way to obtain a stable ID for some 
version of description.

        As automatic code processing is a large part of Common Lisp 
identity as it is presented, and there is a small and easy to define 
chunk of functionality that is missing, I am preparing a CDR on portable
code walking support.

        Before I formally submit a CDR proposal, I want to try to get
some feedback. The current version of the writeup I have is at:
https://gitlab.common-lisp.net/mraskin/cdr-walkability/blob/master/walkability.txt

        Please comment on that proposal, here or via issues or maybe
even merge requests. I will announce the link to the discussion in the
ELS mailing list (as ELS conference seems to be the closest 
approximation to community discussion we have).

        I considered including Trucler API as an option, but currently
I doubt I am able to do it well: mixing a coherent API with multiple 
optional additions that are useful even as single functions is a harder
task. I want to start somewhere.

        Separately, if someone has some proposals on how to make CDR
process used more — or matter more, please share. Probably on cdr-devel
https://mailman.common-lisp.net/listinfo/cdr-devel

        Thank you, goodbye
Michael Raskin