Explanation

Background on why Argot is shaped the way it is. Useful when you want to understand the design rather than accomplish a task.

• Two styles, one engine — why the delegate and annotation styles cannot drift apart.
• Why there is no runtime reflection — what that buys you, and what it costs.
• How optionality is inferred — what the processor can and cannot see about your constructor.
• What counts as a breaking change — the three surfaces a release can break.

These pages assume you have written a command line with Argot already. If you have not, the tutorial comes first.