Skip to content

Conversation

@markshannon
Copy link
Contributor

And infer the class in points-to.
This will allows points-to extensions to more easily compatible across versions,
specifically extensions written for 1.20 will continue to work for 1.21 and later.

@markshannon markshannon force-pushed the python-forward-compatible-points-to-extensions branch from 19e69e6 to 36a8274 Compare March 14, 2019 11:58
@markshannon markshannon changed the base branch from master to rc/1.20 March 14, 2019 11:58
@markshannon markshannon added this to the 1.20 milestone Mar 14, 2019
@markshannon markshannon force-pushed the python-forward-compatible-points-to-extensions branch from 36a8274 to 7296384 Compare March 15, 2019 10:59
…fer the class. Allows points-to extensions to more easily compatible across versions.
@markshannon markshannon force-pushed the python-forward-compatible-points-to-extensions branch from 7296384 to 7213b72 Compare March 15, 2019 11:10
Copy link
Contributor

@taus-semmle taus-semmle left a comment

Choose a reason for hiding this comment

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

LGTM. Is this ready for merging?

@markshannon
Copy link
Contributor Author

Yes. It is just and additional extension, so it can't break anything.

@taus-semmle taus-semmle merged commit 36c7a84 into github:rc/1.20 Mar 21, 2019
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