Back to Examples
- Binding patterns
- Typed binding pattern
- Wildcard binding pattern
- List binding patterns
- Rest binding pattern in list binding pattern
- Mapping binding pattern
- Rest binding pattern in mapping binding pattern
- Error binding pattern
- Rest binding pattern in error binding pattern
- Single use of typed binding patterns
- Single use of typed binding patterns with on fail clause
- Iterative use of typed binding patterns
- List binding pattern in match statement
- Mapping binding pattern in match statement
- Error binding pattern in match statement
- Query expressions
- Sort iterable objects
- Let clause
- Limit clause
- Join iterable objects
- Outer Join clause
- Query tables
- Create tables with a query
- Create maps with a query
- Create streams with a query
- On conflict clause
- Advanced conflict handling
- Iterate over XML with a query
- Nested query expressions
- Destructure records using a query
- Querying streams
- Aggregation
- JSON type
- Access JSON elements
- Access optional JSON elements
- Match statement with maps
- Convert from user-defined type to JSON
- Convert from table and XML to JSON
- Convert from JSON to user-defined type
- Cast JSON to user-defined type
- Resource method typing
- JSON numbers
- JSON to record
- JSON to record with projection
- JSONPath expressions
- Asynchronous function calls
- Named workers
- Sequence diagrams
- Wait for workers
- Strands
- Named worker return values
- Alternate wait
- Multiple wait
- Named workers and futures
- Inter-worker message passing
- Alternate receive
- Multiple receive
- Conditional send
- Inter-worker failure propagation
- Named worker with on fail clause
- Synchronize message passing
- Asynchronize message passing
- Flush
- Fork
Isolated methods
Object methods can be isolated
. An isolated
method is same as an isolated
function with self
treated as a parameter. An isolated
method call is concurrency-safe if both the object is safe and the arguments are safe. This is not quite enough for service concurrency. When a listener
makes calls to a remote
or resource
method,
- • it can ensure the safety of arguments it passes
- • it has no way to ensure the safety of the object itself (since the object may have fields)
import ballerina/io;
class EvenNumber {
int i = 1;
// `isolated` method.
isolated function generate() returns int {
lock {
// Uses `self` to access mutable field `i`
// within a `lock` statement.
return self.i * 2;
}
}
}
public function main() {
EvenNumber e = new;
int c = e.generate();
io:println(c);
}
Executing the above code gives the output below.
$ bal run isolated_methods.bal2
PreviousIsolated variables
NextIsolated objects