Skip to content

1.23: SD-4095 finalize change notes for C/C++ #2434

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

Conversation

felicitymay
Copy link
Contributor

@Semmle/cpp - I've made some small changes to the text in the first commit. The second commit just fixes the sort order in the first table.

I revised the text describing Configuration::hasPartialFlow so that it matched the bullet point in the C# change notes (see #2430). Happy to make changes in either/both PRs but it makes sense for the description to be shared text.

Copy link
Contributor

@geoffw0 geoffw0 left a comment

Choose a reason for hiding this comment

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

Otherwise LGTM. I apologize for having written "mistmatching" in a change note and then copy-pasted it multiple times (well spotted!)

Copy link
Contributor

@jbj jbj left a comment

Choose a reason for hiding this comment

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

Otherwise LGTM

overriding `int explorationLimit()`.
* The data-flow library has been extended with a new feature to aid debugging.
If you want to explore the possible flow from a source, replace
`isSink(Node n) { any() }` with the new `Configuration::hasPartialFlow` predicate.
Copy link
Contributor

Choose a reason for hiding this comment

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

In the second sentence, replace sounds like it should be taken literally, but it shouldn't. Writing isSink(Node n) { any() } was previously a good way to debug data flow, but not everyone did that, so there will be nothing to replace in many cases. Instead, a call to hasPartialFlow should literally replace the call to hasFlow or hasFlowPath.

I propose this text instead for the second sentence:

To explore the possible flow from all sources, including flow that doesn't reach any sink, use the hasPartialFlow predicate on Configuration instead of hasFlow or hasFlowPath.

@aschackmull and @hvitved, what do you think?

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree. The original C# change note was clear.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was trying to reorganize the sentence so that it started with what the user was trying to do, rather than how they'd coded it. As well as making the sentence shorter. Clearly my changes were bad. Would this work any better?

Previously, to explore the possible flow from all sources you could specify isSink(Node n) { any() } on a configuration. Now you can use the new Configuration::hasPartialFlow predicate, which gives a more complete picture of the partial flow paths from a given source, including flow that doesn't reach any sink.

Copy link
Contributor

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

Choose a reason for hiding this comment

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

@felicitymay Your latest proposal sounds good to me. I assume it will still be preceded by "The data-flow library has been extended with a new feature to aid debugging." and followed by "The feature is disabled ...".

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for everyone's patience with this. Now that I'm out of meetings, I'll update this PR and the other change notes.

@felicitymay
Copy link
Contributor Author

My apologies - I've got my self confused. Will amend that last commit after my next meeting 😞

@felicitymay felicitymay force-pushed the 1.23/SD-4095-finalize-change-notes-cpp branch from 507c272 to 4f66608 Compare November 26, 2019 16:42
@felicitymay
Copy link
Contributor Author

I think that the change notes file should now contain the correct wording.

@jbj jbj merged commit 95bceae into github:rc/1.23 Nov 26, 2019
@felicitymay felicitymay deleted the 1.23/SD-4095-finalize-change-notes-cpp branch November 27, 2019 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants