James Clark

@manuranga As a start, could you please categorize each entry in the catalog as an error or a panic? (Ideally, split into two sections.) I strongly suggest that code examples...

I identified quite a number of cases in https://github.com/ballerina-platform/ballerina-spec/issues/807#issuecomment-815430933 for which there is no entry in the jBallerina catalog. These may well be jBallerina bugs.

I would expect the specification only to specify the error type (i.e. distinct type and possibly error detail); I would not expect it to require specific error messages (I don't...

Is any code making using of this inference?

In the new design the type-ids (from distinct types) are performing the role that the reason string played in the old design. Previously, if you used `error`, then you had...

2019R3 and 2020R1 have functional constructors just for errors (so not called functional constructors) https://ballerina.io/spec/lang/2019R3/#section_6.21 2020R2 adds them for xml subtypes and calls them functional constructors. So I would expect...

The concept is that `@deprecated` applies to the same things as `public`. Named parameters can be `public`, so deprecated applies to them. I would suggest a separate heading "Deprecated parameters"...

This should be consistent with what you use for `Deprecated` heading. Some people use h1 as the heading for the document as a whole (i.e. only one h1 in a...

The semantics of an error-arg-list-match-pattern is that each thing specified in the pattern must be present with the specified value in the error. Things that are not specified in the...

It says > if the type descriptor is a union, then this requirement must be satisfied by at least one member of the union and `Foo` satisfies the requirement, so...