Skip to content

[Gardening] Rename getInOutOrLValueObjectType to getWithoutSpecifierType #10790

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

Merged
merged 1 commit into from
Jul 6, 2017

Conversation

CodaFi
Copy link
Contributor

@CodaFi CodaFi commented Jul 6, 2017

Factored out a simple sed to rename this primitive.

Prepares the AST for a future in which more than just inout and
@lvalue need to be stripped off of ephemeral types.
@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 6, 2017

@swift-ci please smoke test and merge

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 6, 2017

Please test with following PR:
apple/swift-lldb#228

@swift-ci Please smoke test

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 6, 2017

⛵️

@CodaFi CodaFi merged commit 9a4fb8c into swiftlang:master Jul 6, 2017
@CodaFi CodaFi deleted the disjunction-junction branch July 6, 2017 18:28
@jrose-apple
Copy link
Contributor

lvalue isn't a specifier. I'm not sure this is the way to go. @rudkx, @rjmccall?

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 6, 2017

I debated calling it something like getWithoutEphemeralType() or getMaterializableBaseType(), but we don't use the terminology in the manifesto consistently throughout the codebase.

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 6, 2017

@lvalue is also a type specifier in the same vein, just one that cannot be spelled.

@jrose-apple
Copy link
Contributor

I'm not sure what your definition of "specifier" is that encompasses "var", "let", "none", "inout", and "lvalue".

@rudkx
Copy link
Contributor

rudkx commented Jul 6, 2017

I don't really see how the old name was particularly offensive or the new one particularly better. I think getMaterializableObjectType() might be an improvement except the result would not always pass the isMaterializable() test since we do not reform tuples with the inout removed from the elements.

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 6, 2017

I don't really see how the old name was particularly offensive

If we're going to be adding new attributes, this name is going to have to be

getInOutOrLValueOrSharedObjectType

@rjmccall
Copy link
Contributor

rjmccall commented Jul 6, 2017

This is temporary, right? We won't actually be introducing a SharedType, and InOutType will be going away. I'm not sure there's much point in renaming stuff.

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.

4 participants