These are chat archives for etorreborre/specs2

6th
Jun 2015
SRGOM
@SRGOM
Jun 06 2015 05:07
@wabash This is reasonably active, please ask
Eric Torreborre
@etorreborre
Jun 06 2015 07:07
@i-am-the-slime you need to get an implicit ExecutionContext. Check out the corresponding section in the user guide
@wabash can you link to a gist or paste your code here. I'm on my phone at the moment but can have a look at your issue when I come back home
SRGOM
@SRGOM
Jun 06 2015 10:06
I think there isn't but throwing it around to confirm: Is there a way to write a test that can confirm that a certain member in production code will not be accessible and throw compile error? What I'm talking about is preventing against a change that makes a member variable public (and allow its subsequent usage).
Eric Torreborre
@etorreborre
Jun 06 2015 11:01
@SRGOM In the latest version you can use the TypecheckMatchers trait
You need specs2-matcher-extra for that
SRGOM
@SRGOM
Jun 06 2015 12:11
Thanks, @etorreborre