Mike Stall

Can you elaborate on the scenario?

As part of this, IAsyncTexlFunction5 should not get its own ServiceProvider.

the challenge here is ambiguity between scalar and tabular. `"abc" in "abcdef" // scalar` `"abc" in [ "abc", "def"] // tabular` Once we say: `abc in U1` we don't know...

This is intentional. Ideally, we want to steer away from untyped and towards stronger typing. Don't say: `U1 < U2` Instead say: `Value(U1) < Value(U2)` We will coerce if one...

Currently, the first matching rule wins (we don't pick the shortest). So if you reorder the BindToInputs, you'll get different behavior. This is definitely not ideal - rule order shouldn't...

I think this is a regression from the attribute cloner work. Table probably needs to map the invoke string directly to the table name.

Re "stable sort", SortParameterNamesInStepOrder calls Array.Sort which is "unstable" (meaning it can reorder the parameters within the same sort-equivalence). https://github.com/Azure/azure-webjobs-sdk/blob/dev/src/Microsoft.Azure.WebJobs.Host/Executors/FunctionExecutor.cs#L810 In practice, this is stable for small values.

The goals here: 1. We want determinism / predictability (safety is a feature) 2. There’s no transactions, so if we have N outputs, we must determine what order to flush...

We identified 2 canonical scenarios for why this is important: 1. Error handling - Are events sent if there's an error in the function ? ``` void Error([Queue] IAsyncCollector q)...

A proposed solution is: 1. the first N (1000?) events get buffered and flushed at the end. A function could emit an unbounded number of events (ie, run for 6...