Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hotfix link in ca02 tutorial #139

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Hotfix link in ca02 tutorial #139

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/courses/core-academy/ca02.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2546,7 +2546,7 @@ dojo: hoon expression failed

## Exercises

- Implement a custom aura, `@uo` (octal/byte encoding). At one level, simply implementing an aura requires no overhead. However, the rune must have a unique parsed format for input, and should have a corresponding output. (The rules around this are laxer for more complex nouns like `set`s and `tree`s.) One format which would be compatible with the restrictions on atom syntax as well as not shadow any current atom types is `0o1234.5670` (`89acbdef` are not valid characters in octal). You can model heavily on `@ux` to implement this aura. (I have a [tutorial](https://github.com/sigilante/curriculum/blob/master/guides/aura.md) which I have not finished for a degree–minute–second implementation.)
- Implement a custom aura, `@uo` (octal/byte encoding). At one level, simply implementing an aura requires no overhead. However, the rune must have a unique parsed format for input, and should have a corresponding output. (The rules around this are laxer for more complex nouns like `set`s and `tree`s.) One format which would be compatible with the restrictions on atom syntax as well as not shadow any current atom types is `0o1234.5670` (`89acbdef` are not valid characters in octal). You can model heavily on `@ux` to implement this aura. (A [tutorial](/language/hoon/guides/aura-guide) is available for a degree–minute–second implementation which you can use as a guide.)
- `++sloe` is intended to receive a `+$type` and return a list of the named arms in that type. Modeling on `++sloe`, produce a gate `++beau` which retrieves each face in the sample of a supplied gate argument and produces a list of them.

```hoon
Expand Down