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

crash in lambdalift, perhaps interaction with extension method receiver stabilizer #11556

Open
martijnhoekstra opened this issue Jun 4, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@martijnhoekstra
Copy link

commented Jun 4, 2019

A port of twitter-util to 2.13.0-RCx crashes with

java.lang.IllegalArgumentException: Could not find proxy for val rw: com.twitter.io.Pipe in List(value rw, method $anonfun$new$15, value <local PipeTest>, class PipeTest, package io, package twitter, package com, package <root>) (currentOwner= value stabilizer$2 )
[error]         at scala.tools.nsc.transform.LambdaLift$LambdaLifter.searchIn$1(LambdaLift.scala:318)

@lrytz suggests reporting even unminimized at https://contributors.scala-lang.org/t/experience-of-migrating-to-2-13-x/3367/7?u=martijnhoekstra.

The full stack trace is at https://gist.github.com/martijnhoekstra/4fe3bd2fbeefceb3b29ee1366aac5c89

You can reproduce with the following branch:

https://github.com/martijnhoekstra/util/tree/bynamecrash

sbt project util-core/test on 2.13.0-RC3 will reproduce the issue. The offending file is util-core/src/test/scala/com/twitter/io/PipeTest.scala

The last commit in that branch (martijnhoekstra/util@5e2e4fb) undoes a workaround that prevents the issue, which could help debugging the issue.

@lrytz

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

I corrected myself in the post on contributors: the stabilizer$2 value is due to scala/scala#5999, not by-name implicits.

@lrytz lrytz changed the title test of twitter-util crashes on 2.13.0-RC3 possibly in by-name implicits. crash in lambdalift, perhaps interaction with extension method receiver stabilizer Jun 4, 2019

@adriaanm

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

Sounds like an issue with the owner chain. Maybe (random guess) an interaction with macros from the test framework?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.