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

Replace julia with Julia in faq when referring to the language. #50103

Merged
merged 1 commit into from
Jun 28, 2023

Conversation

LilithHafner
Copy link
Member

@LilithHafner LilithHafner added the docs This change adds or pertains to documentation label Jun 7, 2023
@@ -22,7 +22,7 @@ On the other hand, language *interoperability* is extremely useful: we want to e

### How does Julia define its public API?

The only interfaces that are stable with respect to [SemVer](https://semver.org/) of `julia`
The only interfaces that are stable with respect to [SemVer](https://semver.org/) of Julia
Copy link
Member

Choose a reason for hiding this comment

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

The language feels a bit weird here. Not your edits, but the sentence originally. Anything you can do to craft it better?

Copy link
Member Author

Choose a reason for hiding this comment

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

Well... I propose to totally write this section in #50105, but the scope of that is way larger than this.

Copy link
Member Author

Choose a reason for hiding this comment

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

How does this sound?

Base and standard library functionality described in the documentation, which is not labeled as unstable (such as experimental and internal), is covered by SemVer." Functions, types, and constants are not part of the public API if they are not included in the documentation, even if they have docstrings.

Copy link
Member Author

Choose a reason for hiding this comment

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

These are separate changes. I'm going to merge this as is, and do the reword in another PR

@LilithHafner LilithHafner merged commit 196956d into master Jun 28, 2023
@LilithHafner LilithHafner deleted the LilithHafner-patch-2 branch June 28, 2023 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants