Finalizing inheritance for fluid-object #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes an error where the first time the fluid-object is being instantiated - its class inheritance is not yet finalized.
Affects cases where a the
with-decoder-simple-clos-semantics
is used without an explicit class (a default fluid-object class is used).Fixes 4 of the test cases:
I've only tested this with SBCL so far.
Haven't tested it in too much effort yet, but as far as i understand - when new classes/slots would appear - the class would go through reinitialization anyways, so I'm not expecting this to have negative effects.
(not an expert though :) )