-
Notifications
You must be signed in to change notification settings - Fork 323
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
Introduce Runtime.Context and methods to manipulate it #6129
Comments
Hubert Plociniczak reports a new STANDUP for the provided date (2023-03-31): Progress: Adding tests, discovering some nuances in the design for further consideration. Preparing the PR for the review. It should be finished by 2023-04-03. Next Day: Next day I will be working on the #6129 task. Gather feedback on the PR, add CLI support |
Hubert Plociniczak reports a new STANDUP for the provided date (2023-03-30): Progress: Following the design and introducing Context and Execution Environment It should be finished by 2023-04-03. Next Day: Next day I will be working on the #6129 task. Continue implementing the changes according to the design. |
Hubert Plociniczak reports a new STANDUP for yesterday (2023-04-03): Progress: Gathering feedback and addressing it. Started investigating partial solution to #6027 as started by James but this one won't be easy, I believe. Some special handling of warnings that changes the default unwrapping/wrapping of self will likely be needed. It should be finished by 2023-04-03. Next Day: Next day I will be working on the #6027 task. Gather more feedback on execution context and try to figure out a solution for #6027. |
As per design, IOContexts controlled via type signatures are going away. They are replaced by explicit `Context.if_enabled` runtime checks that will be added to particular method implementations. `production`/`development` `IOPermissions` are replaced with `live` and `design` execution enviornment. Currently, the `live` env has a hardcoded list of allowed contexts i.e. `Input` and `Output`. # Important Notes As per design PR-55. Closes #6129. Closes #6131.
As per design, IOContexts controlled via type signatures are going away. They are replaced by explicit `Context.if_enabled` runtime checks that will be added to particular method implementations. `production`/`development` `IOPermissions` are replaced with `live` and `design` execution enviornment. Currently, the `live` env has a hardcoded list of allowed contexts i.e. `Input` and `Output`. # Important Notes As per design PR-55. Closes #6129. Closes #6131.
According to the PR-55 specification there shall be:
and then methods to enabled/disable a context:
Together with this change disable all the checks done as a result of
in Input
andin Output
type signatures.The text was updated successfully, but these errors were encountered: