Conversation
4d2bd17 to
321b94c
Compare
|
I think these are great, first 2 down and working through the 3rd now, but these are definitely useful (I'm learning reflection from the 3rd). Perhaps the files could be renamed with a number indicating the order of the tutorials?
The pedant in me finds it odd to start in the middle, go down and then go up in the file view in VSCode. |
RyanJK5
left a comment
There was a problem hiding this comment.
I just gave the tutorials an in-depth look, and I think they are very good! All of the information is accurate. I left some comments, mostly regarding additional pieces of the reflection tutorial worth acknowledging. Thanks for putting these together!
|
@RyanJK5 thanks for the detailed review comments. This is exactly what’s needed for foundational material. Thanks for taking the time. |
RyanJK5
left a comment
There was a problem hiding this comment.
Looks good to me now, thanks for making those changes!
Replaces -DXYZ_PROTOCOL_BUILD_REFLECTION_TUTORIAL=ON as the way to opt into building and testing tutorials/3_reflection.cc.
…nto a signature-string example with a real multi-parameter case - Prefer std::ranges::range auto / std::ranges::views::filter over raw loops where the tutorial's own facilities allow it. - Section 5 was bundling two unequal helpers: a mostly-redundant find-by-name filter and the actually-new signature-string builder. Folded the name filter's only new content (is_const) into section 4, where it fits as a natural extension of the existing enumeration example, and narrowed section 5 to what's genuinely new: reading a member's parameters and rendering them as a signature string. - Widget in section 5 now has a real multi-parameter overload (write(int, double)), so the comma-join logic in simple_signature_string is actually exercised by a test, not just present in the code.
|
I'm going to re-work these tutorials to make them more focused. |
I'm not entirely sure that these tutorials are necessary.
The act of writing them was useful and perhaps they will be useful to readers of the (increasingly novel and technical) code in #95.