Update metaprogramming docs

[nicolasstucki]

[skip test]
[skip test_windows_fast]
[skip community_build]

[b-studios]

What is your motivation of calling it "Quote reflection" and not just "reflection"? I find it a bit confusing since I understand quotation as a mechanism to turn programs into trees, but we do not reflect on the mechanism, but ob the trees themselves.

[nicolasstucki]

I added the Quote in Quote Reflection to distinguish it from scala.reflect and hint at the fact that the reflection is inside the Quotes (i.e. quotes.reflect). I'm fine with Reflection if that is clearer to others.

[b-studios]

Ok, thanks for the explanation. So the point is runtime reflection vs. compiletime reflection, right?

[b-studios]

Renaming might also conflict with PR #10932, so maybe we want to merge that one first?

[nicolasstucki]

Merged and rebased over #10932. Also fixed the Accumulator issue noticed in #10932.

[b-studios]

I'm fine with Reflection if that is clearer to others.

Just to get another opinition, @liufengyun what do you think?

[liufengyun]

I'm fine with Reflection if that is clearer to others.

Just to get another opinion, @liufengyun what do you think?

Reflection seems to be simpler and clearer.

[liufengyun]

While Quote Reflection can work as well, I find the single word Reflection is already clear enough, adding Quote does not seem to add more useful meaning to it. Maybe for simplicity just use Reflection.

[nicolasstucki]

Updated Quote Reflection to Reflection