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

how does SoftUpdate "force bypass cache flag" get set? #753

Closed
wanderview opened this issue Sep 29, 2015 · 2 comments
Closed

how does SoftUpdate "force bypass cache flag" get set? #753

wanderview opened this issue Sep 29, 2015 · 2 comments

Comments

@wanderview
Copy link
Member

Currently the SoftUpdate algorithm takes a "force bypass cache flag". How does this ever get set? Is it needed any more?

@jungkees
Copy link
Collaborator

Currently no callers in the spec sets the force bypass cache flag as pointed. I just left it there for some potential use from implementers (e.g. calls from devtools) as of now.

There's another aspect. Algorithms in other specs are supposed to dispatch their functional events by invoking Handle Functional Event which calls Soft Update at its last step without setting the flag. I'm not sure whether it makes sense but some algorithms may want to call Soft Update directly and with the flag set on their own need.

Does the above usage make sense? Or should we drop the flag?

@wanderview
Copy link
Member Author

That makes sense to me, but a note might help other people reading the spec. Thanks.

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

No branches or pull requests

2 participants