Rename keyword in bounds-safe interface type annotation. #63
Milestone
Comments
dtarditi
added a commit
that referenced
this issue
Oct 4, 2016
This changes the contextual keyword for type annotations in bounds-safe interfaces from `type` to `itype`. This addresses issue #63. Testing: - Checked C tests pass.
mgrang
pushed a commit
that referenced
this issue
Feb 18, 2020
We are about to add enum attributes with AttrKind numbers >= 63. This means we cannot use AttrKind #63 to test for an invalid attribute number in the RAW format anymore. This patch changes the number of an invalid attribute to #255. There is no change to the character of the tests. Differential Revision: https://reviews.llvm.org/D64531 llvm-svn: 365722
dopelsunce
pushed a commit
to dopelsunce/checkedc-clang
that referenced
this issue
Sep 28, 2020
…ypes. (microsoft#63) Return bounds declarations are only allowed for functions with return types that are integer or pointer types. The clang error messages for this situation suggested an array type as a possibility. Functions cannot return arrays, so we've updated the clang error message. Update the corresponding Checked C tests too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bounds-safe interface type annotations currently have the syntactic form
type(type name). The usage of the nametypeis potentially confusing. It could be literally be interpreted that this is specifying a new type for the declared variable. We are going to use the nameitypeinstead to reduce the potential for confusion. This is an abbreviation for interface type.The text was updated successfully, but these errors were encountered: