Skip to content

Comments

Issue 17224 - Remove std.typetuple from the documentation build#5485

Merged
dlang-bot merged 1 commit intodlang:masterfrom
wilzbach:remove-typetuple-from-docs
Jul 18, 2017
Merged

Issue 17224 - Remove std.typetuple from the documentation build#5485
dlang-bot merged 1 commit intodlang:masterfrom
wilzbach:remove-typetuple-from-docs

Conversation

@wilzbach
Copy link
Contributor

Small-scale follow-up to #4968 as triggering deprecation isn't very welcome, but at least we can stop newcomers being confused.

Other PRs: #5484 and dlang/dlang.org#1701

@dlang-bot
Copy link
Contributor

Fix Bugzilla Description
17224 Foreach documentation still refers to TypeTuples, rather than AliasSequences

@andralex
Copy link
Member

Cool! Can you please make sure the name TypeTuple is still present in the AliasSeq documentation? People who see TypeTuple in code must be able to find it in the documentation.

@dlang-bot dlang-bot merged commit df14606 into dlang:master Jul 18, 2017
@wilzbach wilzbach deleted the remove-typetuple-from-docs branch July 19, 2017 19:50
@wilzbach
Copy link
Contributor Author

Cool! Can you please make sure the name TypeTuple is still present in the AliasSeq documentation? People who see TypeTuple in code must be able to find it in the documentation.

I don't think this is necessary. Thanks to the docsarchives.dlang.io they will always immediately find it:

image

image

It's already on top of page 2 and I bet it will go up even higher in the ranking once the page is removed in the next release (and all ddoc / ddox links) are gone.

@CyberShadow
Copy link
Member

I don't think this is necessary.

I don't think that's a good argument against Andrei's idea. Not everyone is going to look for things by doing a global web search.

@andralex
Copy link
Member

Bit of redundancy doesn't harm.

@wilzbach
Copy link
Contributor Author

Bit of redundancy doesn't harm.

Fair enough -> #5636

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants