Nathaniel Cook

See https://github.com/influxdata/flux/issues/220 for adding type classes to accomplish this.

My thinking has been to treat numeric types as polymorphic and let type inference figure out their type based on their usage. Flux is strongly typed, meaning that the type...

Agreed this about perspective. > "numbers' types don't matter....until they do" My hope with Flux is that sense its strongly typed the type is known always by the compiler. The...

Here are is how we are thinking we can implement this: 1. Introduce a new type constraint called NumericDefaultInteger (or something like that) 2. Introduce new NumericLitreal AST and Semantic...

@legomind Could you share your use case? Seeing an example Flux script of what you are trying to do along with the data schema you are using would be very...

Thanks @sanderson for the update, you can follow our progress on this issue here where we have broken out the various steps https://github.com/influxdata/flux/issues/3459

We need a test for this. But it should wait until we have the "new" planner.

You can comma separate as many as you need. ``` |> map(fn:(r) => {r with _value: r._value+2, foo:"bar"} ```

For the type bits see #1378

@jordo1138 Thank you for the request. I expect that we will have an equivalent function in Flux. We are still in the process of porting over many of Kapacitor's features....