-
Notifications
You must be signed in to change notification settings - Fork 146
(torchx/components) Remove dependency to pyre_extensions #1088
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
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
andywag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
402feb2 to
25c0898
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
25c0898 to
52dfa9f
Compare
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
52dfa9f to
2b107c7
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: Pull Request resolved: #1088 There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
2b107c7 to
3cd2d68
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: Pull Request resolved: #1088 There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
3cd2d68 to
93a787e
Compare
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
93a787e to
3d4424b
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
3d4424b to
bd3b8ab
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
bd3b8ab to
42efa1b
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
42efa1b to
0454db3
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
0454db3 to
f39d86c
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
f39d86c to
01ace7e
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
01ace7e to
e273bc3
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
e273bc3 to
d4fd5d8
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
d4fd5d8 to
9814ea5
Compare
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
9814ea5 to
b4d9431
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: Pull Request resolved: #1088 There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
b4d9431 to
d7d5d7d
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: Pull Request resolved: #1088 There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
d7d5d7d to
ec8d802
Compare
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
ec8d802 to
dbb9c78
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77621041 |
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
Summary: There was only a single usage of `pyre_extensions` in the entire code base. Get rid of this dependency by using an `assert` statement rather than `pyre_extensions.none_throws`. Reviewed By: highker Differential Revision: D77621041
Summary: There was only a single usage of
pyre_extensionsin the entire code base. Get rid of this dependency by using anassertstatement rather thanpyre_extensions.none_throws.Reviewed By: highker
Differential Revision: D77621041