James Clark

We should allow them to be specified on the command-line also: an option would specify a value for a single configurable variable, and could be repeated to specify multiple variables.

It's fundamental that a Ballerina table is a 1-dimensional container of records. Furthermore, the record you get out is `===` to the record you put in (as it would be...

Preserving every detail of the original literal in the parsed representation would be hugely complicated (e.g. spaces inside tags, single vs double quotes around attribute literals, numeric escapes - it...

This relates to #35. See specifically https://github.com/ballerina-platform/ballerina-spec/issues/35#issuecomment-1512357879

What this case shows is that we need to distinguish different kinds of usage for module-level types as well as functions. We can say here that - a "call" usage...

See this use case: https://github.com/ballerina-platform/ballerina-lang/issues/30042

Evaluation order must satisfy the constraint that variables (or more module-level identifiers) cannot be referenced before they are initialized. If there's no possible ordering satisfying the constraint, then there's a...

Currently in the spec these are keywords, not predefined or built-int symbols, so `'int` refers to the 3-character identifier `int`, whereas `int` is a keyword, and these are completely unrelated...

I think we still have open the bigger issue, which is whether it would be better to make these not be keywords, but some sort of predefined identifiers. I wouldn't...

I don't think this is fundamentally an iteration issue. Consider ``` decimal x = let var d = 1 in d; ``` This gets a compile-time-error. Given `T x =...