goodboy
goodboy
> error propagation that somehow includes explicit mention of host boundaries in a readable way I think this should mostly be included in a [mailbox / address](https://en.wikipedia.org/wiki/Actor_model#Actor_creation_plus_addresses_in_messages_means_variable_topology) in every message...
In terms of *passing down* values to subactors as is done [with the `statespace` arg right now](https://travis-ci.org/goodboy/tractor/jobs/513632044) I think a better name for this is simply `vars` to pair with...
Re-thinking this after delving into `contextvars` a little more... what we're actually after is a per-process (aka actor) variable scope that can be accessed from all the tasks running in...
I'm almost sold on: - `blah = tractor.ActorVar('blah', default=10)` - `stack = tractor.ContextStack('my_stack')` as module level style declarations that track actor level state and context. For the `ContextStack` I'm thinking...
Interestingly enough the `trio.lowlevel.RunVar` [is a public api](https://trio.readthedocs.io/en/v0.17.0/reference-lowlevel.html#trio.lowlevel.RunVar) though nichey according to `trio` peeps. I'm wondering if just some slight wrapping around this is suitable? - do we need to...
Hmm all this use of *context* leads me to think we should change [our own `Context`](https://github.com/goodboy/tractor/blob/master/tractor/_streaming.py#L15) an an `IPCConext` or something. `ChannelContext`, `TransportContext`? Also pretty sure the `current_context()` in that...
Thinking about this further, I don't think any of this api is really required from the outset :thinking: We can probably get away with just encouraging the use of plain...
Going along in time more I'm thinking `tractor.LocalVar` (or wtv) will have further value when looking at potentially moving the project towards support for [repl-driven-programming](http://mikelevins.github.io/posts/2020-12-18-repl-driven/). For example if we want...
It's probably worth replicating some of the examples from both of these projects for newcomers to see the `trio`/`tractor` way: - `pykka`'s examples: https://www.pykka.org/en/latest/examples/#examples - we can def pwn this...
A much delayed follow up: we'll probably start with an example in the `README` / docs (#163) and add a more extensive tutorial surrounding this later on. In terms of...