Proposal: implicit scope for any function

I am wondering if the notion of implicit scopes, which we already have for resource initializers, can be extended to methods/functions as well.

So basically any method/functions/constructor that has a first argument called scope of type Construct is called without explicitly specifying the scope, and can be customised with "in SCOPE" syntax of course.

This comes up quite a lot, especially in static factory methods. It means that any code that runs in wing always have access to the parent scope that called it. Something that we struggled with in the CDK quite a lot.

The follow up question is what happens in Wing code. If I want to access scope from any method/function, does it mean the compiler will implicitly include an additional first parameter to the function signature. That's a breaking change...

Perhaps all wing functions should always have an implicit scope as the first argument? Don't kill me!

Start by reading the existing implicit-scope behavior for resource initializers, then compare it with method, function, and constructor calls that take a first scope argument of type Construct. Define the semantics for Wing code, including whether scope becomes an implicit parameter and how in SCOPE customization works; the issue is done when these rules and their breaking-change implications are specified.