Skip to content

Conversation

@dtarditi
Copy link
Member

We previously added code to allow type arguments to be omitted at some calls to generic function calls. When type arguments are omitted, void is used as the value for each type argument instead. We allowed type arguments to be omitted at calls in unchecked scopes and checked bounds_only scopes. I think the difference in behavior between different forms of checked scopes will likely be confusing, so require type arguments for all checked scopes.

Testing:

  • We are adding tests to the Checked C repo that checks this behavior.
  • Passed automated testing for Linux.
  • Passed local testing for Windows.

@dtarditi dtarditi merged commit c77f7ef into master Nov 13, 2018
@dtarditi dtarditi deleted the issue572 branch November 15, 2018 17:19
sulekhark pushed a commit that referenced this pull request Jul 8, 2021
Iterate over a BoundsKey set instead of a ProgramVar* set so that the
iteration order does not depend on the address of the program variables.
This fixes the issue, but it is still potentially a problem that the
function depends on the order it iterations over the bounds keys. It is
also likely that other loops over sets of pointers exbibit this same
problem.
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