Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Tasty Reflect API as extension methods testing grounds #19

Open
anatoliykmetyuk opened this issue Jul 30, 2019 · 1 comment
Open

Tasty Reflect API as extension methods testing grounds #19

anatoliykmetyuk opened this issue Jul 30, 2019 · 1 comment
Labels
intent:investigate-behavior You have noticed a behavior that may or may not constitute an issue and want to return to it later

Comments

@anatoliykmetyuk
Copy link
Contributor

Ops classes from tasty.reflect are full of large implicit class constructs. With the current extension methods, it is hard to imagine them being rewritten without boilerplate. Hence they can be a good testing ground to test out the syntax for extension methods, e.g. see scala/scala3#6760 (comment)
@anatoliykmetyuk anatoliykmetyuk added the intent:investigate-behavior You have noticed a behavior that may or may not constitute an issue and want to return to it later label Jul 30, 2019
@anatoliykmetyuk
Copy link
Contributor Author

On the same note, e.g. Flags can be a good candidate for the export feature:

https://github.com/lampepfl/dotty/blob/8b4509d8b49436d01d921b2014ea331d8a8ba845/library/src/scala/tasty/reflect/FlagsOps.scala#L18

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
intent:investigate-behavior You have noticed a behavior that may or may not constitute an issue and want to return to it later
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anatoliykmetyuk