-
Notifications
You must be signed in to change notification settings - Fork 41
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
Clarify the uniqueness of Figure and Plot identifiers #2544
Clarify the uniqueness of Figure and Plot identifiers #2544
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor comment. Looks good.
\lstinline!identifier! must be unique among the \lstinline!plots! in the | ||
\lstinline!Figure! annotation. | ||
The \lstinline!identifier! in \lstinline!Figure! and \lstinline!Plot! is an | ||
optional \lstinline!String! identifier, and is intended to identify the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to say it's a String
here, given the pseudo-code record definitions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Part of the confusion was about the identifiers living in the same namespace as everything else, spelling out String here should make that more clear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, let's see if it the kind of clarification @gkurzbach was looking for, and perhaps see if @HansOlsson wants to have a say on the general style.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think it is fine now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think it is fine now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think it is fine now.
Shall we merge it to MCP/0033? |
Yes, it seems like @gkurzbach has nothing more to add. |
@henrikt-ma you are right. |
No description provided.