Depending what you're trying to do, you could also use some kind of a builder pattern that has a field representation that won't be turned into a real field until it's saved, when it has enough information. Or you could use named:type: with a default name and type and change them later.
On Thu, Oct 13, 2016 at 7:09 AM Esteban A. Maringolo <[hidden email]> wrote:
You can always use #basicNew, hopefully followed by #initialize, but
not strictly necessary if you are doing a lot of internal state
manipulation and can handle "uninitialized" object state.