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

Restore read barrier infrastructure #103

Open
wycats opened this issue Apr 24, 2023 · 0 comments
Open

Restore read barrier infrastructure #103

wycats opened this issue Apr 24, 2023 · 0 comments

Comments

@wycats
Copy link
Member

wycats commented Apr 24, 2023

Before the recent internals overhaul, we had infrastructure that allowed renderers to register a handler that should be called when a reactive value was consumed outside of a tracking frame.

For example, the React renderer uses this infrastructure to warn the user that useReactive is necessary, but only when the consumption in question happens while a React render function is running.

The Vue renderer needs similar infrastructure for a similar reason.

The internals are currently structured to support the read barrier feature; it just needs a more stable public API and implementation.

@wycats wycats moved this to Designing in Starbeam Roadmap Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Designing
Development

No branches or pull requests

1 participant