remove unused imports from aggregate.d

[thewilsonator]

No description provided.

[dlang-bot]

Thanks for your pull request and interest in making D better, @thewilsonator! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the annotated coverage diff directly on GitHub with CodeCov's browser extension
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub fetch digger
dub run digger -- build "master + dmd#9845"

[thewilsonator]

I know this is not the DMD style but that is the only function from there and I think it ought to be in mtype.d anyway, which I plan to follow up in another PR.

[wilzbach]

Walter approved selective top-level imports in the past. I think he just doesn't see much value in them, but from what I gathered he isn't against them. So imho it's more than fine if it's just a few symbols - especially if it's one or two.

[thewilsonator]

Yeah I'm trying to figure out which ones use a single import and mark them so.

With this one specifically I think it should be in mtype.

[wilzbach]

I don't think we should invest time in doing this manually except when writing code which adds new imports. IIRC people have already written tools for this. I think @CyberShadow has one?