Use symbol nomenclature instead of requires, provides...
Instead of referring to the [provided, requires] inputs and outputs of atoms by various names including:
- Argument mappings
- Output mappings
- Input mappings
- ...
- http://
Lets start to follow more standard *compiler* like naming and just refer to these using existing nomenclature where a atom produces symbols that are bound to some value (bound symbols) and an atom may declare symbols (not bound to a value, aka free variables, aka unbound symbols) that it needs for execution (at execution time they will be bound to a value produced by some other atom). This creates a single well-known nomenclature that is more understandable to those who have used or created compilers or languages, or other similar tools previously.
See: http://
Blueprint information
- Status:
- Not started
- Approver:
- Joshua Harlow
- Priority:
- Medium
- Drafter:
- Joshua Harlow
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Start to use symbol nomenclature