Place all objects and passthrough items in the same block, to pass th…

[BenFordTytherington]

Ultimately, it would be good to preserve the blocks things appear in, so if you place a cfg or doc attribute on the top of a block, it is preserved in the final code, but this requires significant rewriting, so work is beginning by slowly grouping things into the same extern block, and passing through docs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (96d3233) to head (e94f57a).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1282   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           75        75           
  Lines        12772     12777    +5     
=========================================
+ Hits         12772     12777    +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[LeonMatthesKDAB]

@BenFordTytherington what is the use-case for this, especially the #[doc()] attribute on extern blocks, what does this translate to in the final cargo doc?

An extern block is not a module, so does the documentation even end up anywhere readable?

[BenFordTytherington]

This seemed like too much of a task, to reorganise code placement in generated output, just for the sake of it, as I had hoped some minor changes could make things easier to place in the same output. I had hoped this would allow for putting cfg attributes on the block, and passing them through to generation more easily, but I think this is not the way, so will close.