-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Feature Request] Update Swift language specification to version 5.5 #2854
Labels
feature-request
Request for new features or functionality
Comments
Thanks for the PR! Can you fix the CI issue? (prettier) |
@hediet I don't know how exactly to fix the issue. Could you give me a pointer to thorough instructions for how to do it? |
Please use prettier to format the files you touched. |
I’m asking where to find prettier
…Sent from my iPhone
On Jan 3, 2022, at 6:30 AM, Henning Dieterichs ***@***.***> wrote:
Please use prettier to format the files you touched.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
You should be able to simply run |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context
Description
Syntax coloring specifications for Swift (swift.ts) are out of date and appear to be from Swift 4 (the most recent version is 5.5). For example, here is a short list of keywords not indexed:
@differentiable(reverse)
async
@escaping
@inlinable
await
associatedtype
@unchecked
rethrows
A list of language keywords can be found here, although the keywords that start with
@
are not listed. There are numerous@
keywords, and it isn't feasible to include all of the ones starting with underscores. However, the ones that start with alphabetic characters should be possible to tabulate.Monaco is the engine behind Google Colab's syntax coloring, and I am concerned because my effort to revive Swift support is negatively impacted by incorrect syntax coloring. Colab is currently restricted to Monaco 0.27.0, so it won't benefit from this correction immediately (the currently version is 0.31.0). Since 0.27.0 was released a few months ago, I expect Google to update to a newer version in the time frame of a few months.
The text was updated successfully, but these errors were encountered: