Skip to content

WIP: Change namedtypes #3147

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

Closed
wants to merge 6 commits into from
Closed

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Sep 21, 2017

This is a second attempt to simplify named types. The first attempt ran into lots of complications when trying to accommodate private members. I decided it's better to start from scratch.

The new attempt tries to keep the basic layout of a NamedType as a combination of prefix and name, without fiddling with designators. Instead we want to base more functionality on the symbol in the type.

Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

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

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Added" instead of "Add")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

The problem is that the assertion in checkNoLeaks might be wrong if
the widened type is erroneous. This happened during editing.
Also

 - rename Fresh flag to NonMember
 - update criterion for phases where refs are symbolic. This used
   to be just before erasure (at resolveSuper) but then other phases
   were inserted after resolveSuper and the test became outdated. It's
   more robust now.
 - simplify Substituters
 - use sym.isOverridable as a test instead of checking whether
   the reference is a WithFixedSym.
@odersky
Copy link
Contributor Author

odersky commented Sep 22, 2017

This PR turned out to be a dead-end, and the approach in #3087 and #3134 is preferable.

The issue is that, as long as we base our tooling on Tasty we cannot define references by their symbols, since these references can go across compilation units. So we need the full distinction between references as names, names with signatures and/or namespaces, and symbols. There's no way around it. We just have to make it as streamlined as we can.

@odersky odersky closed this Sep 22, 2017
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