Skip to content

Conversation

@Redblueflame
Copy link

Rendered

Everything needed for the initial RFC is here, but there will be more to explain in a separate RFC once this one is merged, and working groups are ready.

Reasoning

Experimental features are really needed to prevent incrementing the major / minor version every time a change is made to the user facing APIs, and allow for staged testing before a general availability.

This system is used successfully in rust's standard library, and bring safety for developers, that are sure of the quality of each function called.

@i509VCB
Copy link
Contributor

i509VCB commented Apr 21, 2021

Would probably be good to note that @ApiStatus.Experimental and @Deprecated should both be applied to apis so IDE notification works out.

@Redblueflame
Copy link
Author

Would probably be good to note that @ApiStatus.Experimental and @Deprecated should both be applied to apis so IDE notification works out.

True, but isn't it a little bit too close to the implementation for the scope of this amendment? I'm currently working on a separate RFC for the specifics of the experimental status, in addition to all the other lifetimes.

@Haven-King Haven-King added the amendment A change to an existing RFC label Apr 21, 2021
@TheGlitch76
Copy link
Contributor

Yeah, let's keep the annotation stuff to RFC 13, which formally defines the implementation of experimental features.

@TheGlitch76 TheGlitch76 deleted the branch QuiltMC:qsl-structure June 25, 2021 16:33
@Redblueflame Redblueflame deleted the qsl-structure branch June 25, 2021 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

amendment A change to an existing RFC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants