ARC-0003: Leo and Aleo instructions

[collinc97]

Abstract

The purpose of this ARC is to unify syntax between Leo and Aleo instructions to make it clear what tools developers have at their disposal. We propose several breaking changes to both Leo and Aleo instructions to achieve this goal.

The discussion for this ARC is located at #17

[bendyarm]

This is an improvement on the syntax for both Leo and Aleo Instructions!
I think a 3-column table would be better, to better show how the syntax is being standardized.
How about this:

Leo V1 —>	Leo V2 & Aleo Instructions V2	<— Aleo Instructions V1
---	program	program
∅	interface	∅
mapping	mapping	mapping
circuit	struct	interface
record	record	record
@program function	transition	function
function	function	closure
name.network	name.network	name.network

[collinc97]

This is an improvement on the syntax for both Leo and Aleo Instructions! I think a 3-column table would be better, to better show how the syntax is being standardized. How about this:

Leo V1 —> Leo V2 & Aleo Instructions V2 <— Aleo Instructions V1
--- program program
∅ interface ∅
mapping mapping mapping
circuit struct interface
record record record
@program function transition function
function function closure
name.network name.network name.network

This is a great idea Eric. Making the change now!

[evanmarshall]

Hi, just a couple questions about the new interface.

1. Can a program implement multiple interfaces?

2. How will importing interfaces work? Is this planned to work with the Aleo Package Manager?

[howardwu]

Hi, just a couple questions about the new interface.

1. Can a program implement multiple interfaces?
2. How will importing interfaces work? Is this planned to work with the Aleo Package Manager?

+1, I'm also still working through how to design interfaces, especially for Aleo instructions. Let's get this document merged and continue discussion on interfaces in the Discussion page.

[bendyarm]

Looks good to me!
If we want to get away from "breaking changes"
we could say something like "changes from the previous prerelease version" but that doesn't seem too important to me.

[collinc97]

ARC-0003: Leo and Aleo instructions

Looks good to me! If we want to get away from "breaking changes" we could say something like "changes from the previous prerelease version" but that doesn't seem too important to me.

We can still iterate on the document once it is living.