Skip to content

Move DiagnosticReporter to errors.d#9484

Merged
dlang-bot merged 1 commit into
dlang:masterfrom
jacob-carlborg:move-diagnostic-reporter
Mar 25, 2019
Merged

Move DiagnosticReporter to errors.d#9484
dlang-bot merged 1 commit into
dlang:masterfrom
jacob-carlborg:move-diagnostic-reporter

Conversation

@jacob-carlborg

@jacob-carlborg jacob-carlborg commented Mar 24, 2019

Copy link
Copy Markdown
Contributor

It's more suitable located in errors.d since it's part of the error handling. It can also be used in other places then the lexer in the future.

Part of #9480.

@jacob-carlborg jacob-carlborg added the Severity:Refactoring No semantic changes to code label Mar 24, 2019
@dlang-bot

Copy link
Copy Markdown

Thanks for your pull request and interest in making D better, @jacob-carlborg! 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#9484"

@jacob-carlborg jacob-carlborg force-pushed the move-diagnostic-reporter branch from 9a761cd to 203bdf3 Compare March 24, 2019 19:59
@thewilsonator

Copy link
Copy Markdown
Contributor

Semaphore fails with

Performing "debug" build using /home/runner/dlang/dmd-2.085.0/linux/bin64/dmd for x86_64.
dmd:root ~master: target for configuration "library" is up to date.
dmd:lexer ~master: building configuration "library"...
dmd:parser ~master: building configuration "library"...
dmd:frontend ~master: building configuration "library"...
lexer ~master: building configuration "application"...
lexer.d(21,32): Error: undefined identifier StderrDiagnosticReporter
/home/runner/dlang/dmd-2.085.0/linux/bin64/dmd failed with exit code 1.

@jacob-carlborg jacob-carlborg force-pushed the move-diagnostic-reporter branch from 203bdf3 to 88f6aee Compare March 25, 2019 10:17
@jacob-carlborg

Copy link
Copy Markdown
Contributor Author

Fixed, hopefully.

It's quite annoying that there seems to be no easy way to run all the test. I'm guessing it's because different tests are run on different CI platforms.

@jacob-carlborg

Copy link
Copy Markdown
Contributor Author

I don't see why Semaphore is failing.

@jacob-carlborg jacob-carlborg force-pushed the move-diagnostic-reporter branch from 88f6aee to bdd4a5f Compare March 25, 2019 10:50
It's more suitable located in `errors.d` since it's part of the error
handling. It can also be used in other places then the lexer in the
future.
@jacob-carlborg jacob-carlborg force-pushed the move-diagnostic-reporter branch from bdd4a5f to e02dd04 Compare March 25, 2019 11:34
@WalterBright

Copy link
Copy Markdown
Member

class DiagnosticReporter looks like hundreds of lines of code that does nothing. Why is this even there?

@WalterBright

Copy link
Copy Markdown
Member

Apparently it was added by #9350

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

Labels

Merge:auto-merge Severity:Refactoring No semantic changes to code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants