Explicit dependency management

[dphfox]

Implements #111, #168, and #35. First steps towards #205.

• :get() will now error when called.
• Fusion.peek will retrieve the value of any state object without adding dependencies, or pass through constants.
• Dependency providers will wrap peek in dependency management code to generate use callbacks for use by the API consumer. These should also pass through constants.

[krypt102]

Lovely! I haven't read through the PR but I hope it contains the use function within computed! (nevermind it was like 6 lines changed)

Small thing, maybe use the term solves to make github detect that this PR will close the labeled issues. For a list you'll need to put the prefix before every issue (e.g. solves [a], solves [b])

[dphfox]

Lovely! I haven't read through the PR but I hope it contains the use function within computed! (nevermind it was like 6 lines changed)

Small thing, maybe use the term solves to make github detect that this PR will close the labeled issues. For a list you'll need to put the prefix before every issue (e.g. solves [a], solves [b])

Yeah, I'm only just starting work now that the prereq backlog is sorted, hence draft status. This won't take long to implement and should be an easy one-man job.

I'm currently focusing on public API work (docs, types, messages) before doing the simple private work.

[krypt102]

I'm currently focusing on public API work (docs, types, messages) before doing the simple private work.

nice! I might make a small PR which fixes all of the stuff on the docs unless you’ve already got that.

[dphfox]

I'm currently focusing on public API work (docs, types, messages) before doing the simple private work.

nice! I might make a small PR which fixes all of the stuff on the docs unless you’ve already got that.

I'll be fine - there's some nuance required for the tutorials.

[krypt102]

Also didn’t realise you could link prs and issues so that’s my bad!

[krypt102]

I'll be fine - there's some nuance required for the tutorials.

oh okay! I’ll find some other issues or things to work on in the meantime

[krypt102]

The most recent commit poses an interesting question. For the for* objects, will use now be the first parameter followed by the others (the key in ForKeys, the value in ForValues and both in ForPairs)?

[dphfox]

The most recent commit poses an interesting question. For the for* objects, will use now be the first parameter followed by the others (the key in ForKeys, the value in ForValues and both in ForPairs)?

Yes. Having the use callback in a stable position seems to be a good idea. This is a massively breaking change anyway, so better to do the right thing than the compatible thing.

[dphfox]

Probably done for the day at this point. I haven't yet tested any of this code, but this should roughly be along the right lines.

Will need to update tests and benchmarks too.

[krypt102]

Nice! If you need help lmk haha but it should be easy enough as u said. I’m gonna most likely work on some others today during class

[krypt102]

One small thing you probably forgot is to change Attributes to use isState instead of xtypeof, I didn’t notice that in the last commit that’s all, the rest looks amazing!

[dphfox]

This should be ready now. I know there's a few places where I could perhaps do more caching work, but we can do that in the future - it's more important to merge a working version than an optimal one, I think.

[krypt102]

One small change I found here, if it's intentional please let me know!