-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Drop AndTypeTree and OrTypeTree #5935
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
Conversation
d6ff493
to
6ba9bc7
Compare
Quite an impressive savings in LOC. Also fixes some holes where illegal wildcard types went undetected. |
test performance please |
performance test scheduled: 1 job(s) in queue, 1 running. |
Performance test finished successfully: Visit http://dotty-bench.epfl.ch/5935/ to see the changes. Benchmarks is based on merging with master (2b0e4a1) |
|
Drop previous checking in Parser. The idea is that the parser should follow the syntax. Checking conditions that are not reflected in the syntax should come later.
Simplify and cover cases that were missing (see gadt-GadtStatic.scala).
I believe the test is counter-productive. It leads to ossification by pedantically insisting on the status quo. If we want to test tasty extractors we need to find a way that tests it so that we can still change constrructors and extractors.
It does not seem to serve a purpose. The only test where it was used does not really make sense.
6ba9bc7
to
b902306
Compare
@nicolasstucki Can you finish this PR? We still need to re-enable the tasty-extractor test and there are two issues open in the Tasty reflect framework 9see my comments above). |
@odersky I made the changes. You should have a quick look at my commits. |
@nicolasstucki Your changes LGTM |
Drop special treatement and AndTypeTree and OrTypeTree. Replace with regular InfixOp/AppliedTypeTree nodes.