feat[class-creator]: Add loan pattern to incapsulate life cycle of ClassCreator inside API

[poldinik]

#181

[dmlloyd]

I like the idea of this change (note that a few of the APIs I have added to this project in the past also use this pattern, and the new JDK classfile API does as well). But IMO we should apply it more uniformly, as opposed to haphazardly applying it to different places with no real overall plan.

[poldinik]

I like the idea of this change (note that a few of the APIs I have added to this project in the past also use this pattern, and the new JDK classfile API does as well). But IMO we should apply it more uniformly, as opposed to haphazardly applying it to different places with no real overall plan.

How we can lead ahead this feature more systematically? Which step you see I need to follow to propose it and contribute? I mean something like roadmap o design specification before actual develop and avoid waste of time if stakeholders don't like implementation

[dmlloyd]

This is a good question that I do not have an answer to. Maybe start with a high-level proposal that encompasses the existing API usages for method, class, and block creators, and go from there?