Closed zdne closed 9 years ago
@zdne Done making comments. Looks great!
I'm done too! The mind map image could have more colours, but it's good enough for now.
We should use camelCase.
The more I think, the more I am convinced that Named Type
should probably inherit or should be same as Property Member
.
camelCase it is
The more I think, the more I am convinced that Named Type should probably inherit or should be same as Property Member.
Please elaborate.
I have hopefully added more clarity to the AST map (however the principal layout does stay the same):
@honzajavorek @fosrias per your request I have extended the JSON AST example
The more I think, the more I am convinced that Named Type should probably inherit or should be same as Property Member.
@zdne @pksunkara I disagree. Property Member inherits from Value member which would then imply a Named Type would have a value and an inline description. I think it is correct as it is.
@fosrias @honzajavorek @pksunkara I am done with fixes based on your review remarks. If there are no further remarks.
I would like @honzajavorek or @pksunkara to merge this PR (as they need to be familiar with the MSON AST the most).
Thank you!
@zdne One typo I noted. After that fine by me for @honzajavorek or @pksunkara to merge.
Also spotted "fot", otherwise good.
@zdne @fosrias @honzajavorek The MSON AST types are circular.
Type Section needs Member Type which needs Value Member which needs Type Section.
I can use a forward declaration in C++, but just wanted to make sure you guys know this.
I can use a forward declaration in C++, but just wanted to make sure you guys know this.
Yes, I am aware of this (read: this is intended). I am not sure whether a forward declaration is the way to go but this is not the right place to discuss the C++ implementation. We can do it in person tomorrow, or lets do it over a gist or a PR proposal.
For @fosrias, @honzajavorek and @pksunkara to review.