Closed romac closed 7 years ago
@samarion @mantognini @jad-hamza Any idea what might be going wrong there?
My bad, the testcases are actually missing some imports. Everything runs fine now.
If the issue was simply a missing import, we should probably fire a nicer error than this monstrosity into the user's face.
Agreed. Here the problem was that the List.apply method that was resolved was the one from the scala.collection instead of stainless.collection.List.
Maybe we can even figure out a way to override the standard prelude with our own, which would put stainless.lang. and stainless.collection. in scope.
I know there is an option to do that with the Typelevel Scala programmer but I don’t whether that’s the case for Lightbend Scala as well.
On 27 Oct 2017, at 10:43, Marco Antognini notifications@github.com wrote:
If the issue was simply a missing import, we should probably fire a nicer error than this monstrosity into the user's face.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
With my branch in #78, the following benchmark yields different results with the extraction test suite and the verification pipeline that runs when invoking stainless on its own (either from the command-line or through
sbt runMain
.I tried performing the extraction in the test suite using
VerificationComponent.extract
, but am still getting the same error.Any idea what could be going wrong there?
Extraction test suite
stainless-scala/it:testOnly stainless.ExtractionSuite
Verification pipeline
runMain ConstructorArgsBoxing2.scala