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

Improve readme to include experimental features #7

Merged
merged 2 commits into from
Mar 6, 2024

Conversation

jabraham17
Copy link
Member

Improve readme to include experimental features

Signed-off-by: Jade Abraham <[email protected]>
Copy link
Contributor

@ShreyasKhandekar ShreyasKhandekar left a comment

Choose a reason for hiding this comment

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

Thanks for Updating this Jade!
In terms of experimental features I had a small comment about adding a part to tell users how to opt in. I think for the short term this is okay as is.

In the longer term I believe we should not have experimental features published to users for the stable release, rather we should use the VS Code Marketplace's ability to have a Beta/pre-release version of the extension to allow users who are interested to opt in to these features, till they are stable enough for the stable release.

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
@jabraham17
Copy link
Member Author

In the longer term I believe we should not have experimental features published to users for the stable release, rather we should use the VS Code Marketplace's ability to have a Beta/pre-release version of the extension to allow users who are interested to opt in to these features, till they are stable enough for the stable release.

While to some extent I agree with that, its not within the control of the extension for when these features are available. The "experimental features" are fully baked language server features, its just that the dyno resolver needs to be more feature complete before these are on by default

@ShreyasKhandekar
Copy link
Contributor

ShreyasKhandekar commented Mar 6, 2024

Okay I see, I was misunderstanding the experimental nature of the features. I think we can keep them this way in that case.

Signed-off-by: Jade Abraham <[email protected]>
@jabraham17 jabraham17 merged commit 2380d70 into chapel-lang:main Mar 6, 2024
@jabraham17 jabraham17 deleted the improve-readme branch March 6, 2024 21:38
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