Skip to content

SIL: Terminology change: [fragile] => [serialized] #8407

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

slavapestov
Copy link
Contributor

Also, add a third [serializable] state for functions whose bodies we
can serialize, but only do so if they're referenced from another
serialized function.

This will be used for bodies synthesized for imported definitions,
such as init(rawValue:), etc, and various thunks, but for now this
change is NFC.

@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@slavapestov slavapestov force-pushed the rename-everything-without-asking-permission branch 2 times, most recently from 073a136 to 31ddabb Compare March 29, 2017 09:29
@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 0cead346849da2599465d28ff4f500c21251287d
Test requested by - @slavapestov

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 0cead346849da2599465d28ff4f500c21251287d
Test requested by - @slavapestov

// Serialized if referenced from another serialized function.
IsSerializable,
// Always serialized.
IsSerialized
Copy link
Contributor

Choose a reason for hiding this comment

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

IMHO, IsSerialized is not a very good choice for a name. It is too easy to think that something was serialized by the SIL serializer already. I'd prefer names which would use a different verb. Or they could indicate the possibility, e.g. NotToBeSerialized, CanBeSerialized, ShouldBeSerialized....

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's better than "fragile" no? :-)

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, it is better than "fragile", but not good enough, IMHO ;-)

@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

Also, add a third [serializable] state for functions whose bodies we
*can* serialize, but only do so if they're referenced from another
serialized function.

This will be used for bodies synthesized for imported definitions,
such as init(rawValue:), etc, and various thunks, but for now this
change is NFC.
@slavapestov slavapestov force-pushed the rename-everything-without-asking-permission branch from 31ddabb to 8fe8b89 Compare March 29, 2017 23:48
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

1 similar comment
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test Linux

@slavapestov
Copy link
Contributor Author

@swift-ci Please test Linux

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 31ddabb
Test requested by - @slavapestov

@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test Linux

@slavapestov
Copy link
Contributor Author

First a flaky SwiftPM test now Foundation, neither related to my change which is NFC. Sigh.

@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test Linux

@slavapestov
Copy link
Contributor Author

@shahmishal @erg Can one of you guys just click the magic merge button? This patch is just a giant NFC renaming and delaying it for another day will just mean more fixing merge conflicts and rebasing.

@slavapestov slavapestov merged commit 695a8d2 into swiftlang:master Mar 30, 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.

3 participants