ligo/gitlab-pages/docs/contributors/big-picture/overview.md
2019-06-03 18:48:54 +02:00

17 lines
741 B
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
id: overview
title: Overview
---
After going through the design principles and a few considerations linked to them, getting the Big Picture needs diving in technical matters.
![LIGO Overview](/img/big-picture-overview.png)
As shown in the Schema, LIGOs compiler is separated in roughly 3 separate parts:
- The Middle End. This is the core of LIGO. It defines its core data-structure (the Common AST), and its type-checking algorithm.
- The Front End. This is the bridge between a given syntax and the Common AST.
- The Back End. This is the bridge between the Common AST and a given compilation target. Currently, our only target is Michelson, but well also target Marigold, and if Tezos moves to Web Assembly, Web Assembly.