Skip to content

Conversation

@nicolasstucki
Copy link
Contributor

Using the cake pattern made it easy to split and keep into smaller files.
But this comes at a cost:

  • Extra bridges
  • Not knowing where to find stuff
  • Hard to update
  • Inability to use opaque types and proper extension methods

The downside is that we will have a larger Reflection.scala file, but
it will be proportional to the size of CompilerInterface.scala which has
been easier to manage than the cake.

Note: scala.tasty.Reflection did not have any API changes.

Using the cake pattern made it easy to split and keep into smaller files.
But this comes at a cost:
 * Extra bridges
 * Not knowing where to find stuff
 * Hard to update
 * Inability to use opaque types and proper extension methods

The downside is that we will have a larger `Reflection.scala` file, but
it will be proportional to the size of `CompilerInterface.scala` which has
been easier to manage than the cake.

Note: `scala.tasty.Reflection` did not have any API changes.
@nicolasstucki nicolasstucki marked this pull request as ready for review January 30, 2020 15:57
Copy link
Contributor

@liufengyun liufengyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@liufengyun liufengyun merged commit 079a211 into scala:master Jan 30, 2020
@liufengyun liufengyun deleted the uncake-tasty-reflection branch January 30, 2020 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants