tommie

@0xPIT Sorry I didn't reply to this back in _the_ December. I want to avoid this becoming the place where patches are introduced. I'd hoped CK would have an official...

Drive-by comment by another user: this looks like a nice simplification.

I wonder if this API would be helpful: ```go type PathContext struct { bt *BTree hint PathHint } func (c *PathContext) Delete(key interface{}) interface{} { return c.bt.DeleteHint(key, &c.hint) } func...

Drive-by comment: thanks for making this! Scary to see that TypeScript metaprogramming goes this deep (path generation). Hoping to help test this. * Would it be possible to make `stricterTypes`...

> I think it may be better to wait for the stricter types to get mature enough? I agree with the sentiment, but I'm guessing the PR is more likely...

Some thoughts after converting a PoC: * Using `type Store = typeof store` and `InjectionKey` makes more sense now. Sadly that doesn't have a nice fallback for when stricter types...

Thanks for the fixes! > createStore() now accepts the virtual parameter stricterTypes in its options: I needed to move the `stricterTypes` overload first (just like with `useStore`) for type inference...

Drive-by comment: thanks for working on this! I don't understand the generics involved in `ExtractObjects`, but I'm wondering if it would be possible to skip the separate `S` type param...

Thanks, Erik. > A complicating factor was that alternative Compose implementations of today typically focus on runtime aspect of workflow (as opposed to build) What do you mean by "alternative...

@Niek Agreed. I thought I made a PR for this spec change proposal, but apparently I never committed it. It's identical to yours, except, as with runtime secrets, there's a...