James Clark

@hasithaa I agree with your comment. The case I am not sure about is ``` int[1] | int[2] x = [17]; ``` In this case, the list constructor is compatible...

Here https://ballerina.io/spec/lang/master/#section_7.1 we say > The precedence for action-or-expr is the same as for expression, with the addition that the -> operator used in a client-remote-method-call-action has the same precedence...

We should allow this.

Allowing `local-no-init-var-decl-stmt` is harmless, but pointless, since the statement to initialize the variable will get an unreachable error.

My thoughts on these: - `@embed` makes the program differently from how the spec says it should behave - `configurable` is mixing two different concepts; we don't necessarily want things...

C is adding similar functionality - as #embed directive https://thephd.dev/finally-embed-in-c23

@sameerajayasoma My concern is that the language already specifies clear semantics for: ``` final string s = '''; ``` It is that the `s` is initialized to the empty string...

Why can't we do this with a regular library function?

Why is this a spec issue?

It doesn't say that an intersection type is the only way to describe an error that induces a non-empty set of type-ids. I agree it could be more helpful.