Skip to content

Partially revert #303 until #317 is resolved #318

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

Merged
merged 1 commit into from
Feb 13, 2018

Conversation

wilzbach
Copy link
Member

This reverts the functional changes of #303, but keeps the refactoring.

Motivation:

In #317 we might figure out a way to be smarter about lines without a semi-colon,
so publishing this now would limit our abilities to change the behavior later.


The master-stable branch-off is supposed to happen in two days, so a quick pull would be appreicated.
Thanks!

CC @CyberShadow @marler8997 @WebDrake

@dlang-bot
Copy link
Contributor

Thanks for your pull request, @wilzbach!

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.

@marler8997
Copy link
Contributor

Good idea, by reverting the new feature for now we can delay the decision on what to support.

@dlang-bot dlang-bot merged commit 5cc9864 into dlang:master Feb 13, 2018
// Revert https://github.com/dlang/tools/pull/303 until
// https://github.com/dlang/tools/pull/317 has been resolved
//if (code.length > 0 && code[$ - 1] != ';')
//code ~= ';';
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't a reversion of #303, it's a (breaking) change relative to previous behaviour.

Until #303, a terminating semicolon would always be added. What #303 changed was to stop that happening in cases where there was already a terminating semicolon.

@WebDrake
Copy link
Contributor

This reverts the functional changes of #303, but keeps the refactoring.

@wilzbach I would like to understand how you came to the conclusion that you were reverting the functional changes of #303, because I thought I'd been pretty clear (and detailed) about what that PR was changing and why.

It wasn't #303 that introduced the idea of auto-appending a ; to code provided by --eval.

@wilzbach wilzbach deleted the partially-revert-303 branch February 13, 2018 19:55
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.

5 participants