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

Reduce compiler verbosity when compiling code with Expecty #1

Closed
emchristiansen opened this issue Feb 6, 2013 · 5 comments
Closed
Assignees

Comments

@emchristiansen
Copy link

First off, Expecty is great. I've converted 90% of my assertions to Expecty calls. Thanks!

Using SBT and building a project with Expecty, the compiler prints an AST for each call site where Expecty is used. This makes it hard to find useful compiler messages buried in the noise.

If there's some standard trick to make this stuff go away, please mention it on the main page. Otherwise, please modify Expecty so it has a quiet mode.

@pniederw
Copy link
Owner

pniederw commented Feb 8, 2013

Thanks for the feedback. You are right, this output shouldn't be shown by default.

@pniederw
Copy link
Owner

Apparently, some environments show compiler info logging by default, and there is no compiler debug log level (at least not for macros). To solve this problem, I've introduced an org.expecty.debug system property, which needs to be set to true for AST logging to occur. This is now available in the fresh Expecty 0.10 release. Anyway, thanks for the pull request!

@ephemerist
Copy link

I'm still seeing logging for "RangePosition found!" in expecty 0.10. Could that one be made conditional on the debug property too?

@emchristiansen
Copy link
Author

I'm also seeing "RangePosition found!".

@pniederw
Copy link
Owner

Sure thing. Mind to open another issue or send a pull request?

som-snytt pushed a commit to som-snytt/expecty that referenced this issue May 15, 2024
cross build to Scala.JS and Scala Native
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants