-
Notifications
You must be signed in to change notification settings - Fork 65
Doc update2 #143
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
Doc update2 #143
Conversation
@@ -16,7 +16,7 @@ Implementation status of compiler and language features in Embedded Swift, compa | |||
| Metatypes | No, currently only allowed as unused arguments (type hints) | | |||
| Untyped throwing | No, intentionally unsupported long-term (typed throwing should be used instead) | | |||
| Weak references, unowned references | No | | |||
| Non-final generic class methods | No, intentionally unsupported long-term, see <[Embedded Swift -- Non-final generic methods](NonFinalGenericMethods.md)>| |
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.
can we use a docc style link here?
@@ -27,4 +27,4 @@ Note that there are no behavior changes in Embedded Swift compared to full Swift | |||
|
|||
## Further resources | |||
|
|||
The above lists are describing features that are removed from Embedded Swift *by design*. Since Embedded Swift is currently an experimental preview, there might also be features that are not yet implemented. See the in-development status at [Embedded Swift -- Status](EmbeddedSwiftStatus.md). |
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.
same note about docc style link
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.
I kept the same link type as before, just fixing the name so it points to the right place.
I checked if I could specify a name when using the <doc: > construct but did not find anything in the doc.
I believe in the name would automatically be the name of the target document, which I'm fine with.
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.
I did change the link, it indeed looks cleaner
Thanks, @ebariaux, these are all great changes! |
Mostly fixes for typos and broken links