Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

std.utf: clean imports #2669

Merged
merged 1 commit into from Nov 9, 2014
Merged

std.utf: clean imports #2669

merged 1 commit into from Nov 9, 2014

Conversation

9il
Copy link
Member

@9il 9il commented Nov 9, 2014

import std.conv : to;
import std.exception;
import std. string : format;
import core.exception : AssertError;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This same block of imports seem repeated across many unittests; how about merging them into a single version(unittest) block?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

version(unittest) global import is huge headache while testing new scoped imports for the same modules.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Maybe it's OK then.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All PRs like this are first step. There will be second step after std.range package, and maybe third step, after 'std.algorithm' package.

@quickfur
Copy link
Member

quickfur commented Nov 9, 2014

Other than that, LGTM.

@quickfur
Copy link
Member

quickfur commented Nov 9, 2014

Auto-merge toggled on

quickfur pushed a commit that referenced this pull request Nov 9, 2014
std.utf: clean imports
@quickfur quickfur merged commit 05663e8 into dlang:master Nov 9, 2014
@9il 9il deleted the utf branch November 9, 2014 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants