eejbyfeldt commented on pull request #27153: URL: https://github.com/apache/spark/pull/27153#issuecomment-872867876
I looked some more at this and realised what the problem with `Tuples` is, it guess it all related to when a value class it its underlying type and when it is not https://docs.scala-lang.org/overviews/core/value-classes.html#allocation-details Based on this it seems something like the approach of the PR https://github.com/apache/spark/pull/22309 by @mt40 would be needed to handle all cases correctly. To me it also makes sense that a AnyVal would give the same schema regardless of where it is used like that PR. So unless there is someother good suggestion on this, that is the approach I am going to persue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
