I'm running into some kind of a problem here.

LMS defines the TupledFunctions as a way to work with lambda's with multiple arguments. So the lambda conversion is done by packing the arguments into a tuple at language level and then unpacking them in the corresponding generators..

This removes the ability to reason about lambdas with multiple arguments and lambdas with 1 tuple argument separately which might be okay for small DSLs but I'm not sure if this would be intended behavior for a DSL that aims to provide most of Javascript's functionality.

So, is this a bug or intended behavior? If so how do we fix it (I'm perfectly willing to look for a solution with you), if not, what is the intended work-around? Seeing as Javascript doesn't have tuples maybe removing the tuple functionality and strictly working with Structs or Adts is sufficient?

Thanks!