James Clark
James Clark
@Kishanthan Please have a look at https://ballerina.io/spec/lang/master/#section_8.2
Note that `main` is not a language-level concept. At the language level all you have is a root module. Running a program is just a matter of initializing the root...
It's an implementation detail: you can hide or expose in whatever way you feel appropriate.
The terminology of "key-value pairs" sounds like it comes from Go's structured logging. In Ballerina terminology, what you are providing is a mapping.
In the spec, *member type* is italicized. It's defining a term "member type of K in T" which will be used later (in 6.14). Suppose T is `record { int...
Hmm. listener-decl is consistent with module-const-decl.
#172 proposes adding `concat`, which makes this a bit easier (in conjunction with `...` spread operator). I would do that before this. I think the bar for adding functions to...
Just to be clear if L is a list of lists, you can flatten it into a list with `array:concat(...L)` (same as `string:concat`.) But it’s not terribly convenient for this...
The user should be able to push elements to a sliced array. Arrays in Ballerina never share storage. So in this case, after calling `slice`, mutating `arr` should not mutate...