Concurrency Primitives

Concurrency theory, Go scheduler references

Usage Guidelines

1. Model Choice: Choose between shared memory and message passing based on language goals
2. Memory Model: Define memory ordering semantics clearly
3. Scheduling: Design scheduler with fairness and efficiency in mind
4. Integration: Ensure GC and concurrency work together correctly
5. Testing: Build concurrency stress tests from the start

Output Schema

{
  "type": "object",
  "properties": {
    "model": {
      "type": "string",
      "enum": ["shared-memory", "message-passing", "actor", "csp"]
    },
    "primitives": {
      "type": "array",
      "items": { "type": "string" }
    },
    "schedulerType": {
      "type": "string",
      "enum": ["os-threads", "green-threads", "work-stealing", "cooperative"]
    },
    "generatedFiles": {
      "type": "array",
      "items": { "type": "string" }
    }
  }
}