Skip to content
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

Checked C spec updated with replacing void * #311

Merged
merged 7 commits into from
Sep 6, 2018
Merged

Checked C spec updated with replacing void * #311

merged 7 commits into from
Sep 6, 2018

Conversation

Prabhuk
Copy link
Collaborator

@Prabhuk Prabhuk commented Aug 28, 2018

No description provided.

dtarditi and others added 6 commits July 13, 2018 12:13
Replaced syntax of the function specifier for polymorphic bounds safe interface functions from itype(for_any(...)) to itype_for_any(...).

Pending:
Needs further explanation about where the type variables are expected and implementation details.
Copy link
Member

@dtarditi dtarditi left a comment

Choose a reason for hiding this comment

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

There are some areas related to itype_for_any that need further updates.

@@ -64,10 +64,13 @@
count,
dynamic_bounds_cast, _Dynamic_bounds_cast,
dynamic_check, _Dynamic_check,
for_any, _For_any,
Copy link
Member

Choose a reason for hiding this comment

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

I think the need keyword for itype_for_any needs to be added here.

@@ -22,8 +22,8 @@ \section{New keywords}
begin with two underscores \cite[Section 7.1.3]{ISO2011}. The following
new keywords are introduced:
\begin{lstlisting}
_Array_ptr _Checked _Dynamic_check _Nt_array_ptr _Nt_checked _Ptr
_Where _Unchecked
_Array_ptr _Checked _Dynamic_check _For_any _Nt_array_ptr _Nt_checked
Copy link
Member

Choose a reason for hiding this comment

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

The new itype_for_any keyword needs to be added here.

For parameters and returns that have bounds-safe interfaces, the
bounds-safe interfaces are used for their types.

When a function with a generic bounds-safe interface is not
Copy link
Member

Choose a reason for hiding this comment

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

This paragraph needs to be updated.

Copy link
Member

@dtarditi dtarditi left a comment

Choose a reason for hiding this comment

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

Looks good!

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