git.iko.soy/urbit.org
on master help sign in
Merge pull request #178 from cxk280/dev

Make bulleted list for exercises in first two Urbytes

commitb9b7f3b4eabf648c4f7e9a33912bc6c1eabd2148 authorFang <Fang-@users.noreply.github.com> dateFri 23 Jun 2017, 13:43 (9 years ago) parentf92794f40e52ae
3 files changed+14−11
compare with master
unifiedsplit
docs/arvo/network.md+1−1 docs/byte/0.md+8−5 docs/byte/1.md+5−5
docs/arvo/network.md+1−1
@@ -65,7 +65,7 @@ didn't exist. This is a slightly hacky way of printing to the console,
6565but we'll get to the correct way later on.
6666
6767But what does `++poke-noun` produce? Recall that `^-` casts to a type.
68−In this case, it's declaring that end result of the function will be of
68+In this case, it's declaring that the end result of the function will be of
6969type `{(list) _+>.$}`. But what does this mean?
7070
7171The phrase to remember is "a list of moves and our state". Urbit is a
docs/byte/0.md+8−5
@@ -271,11 +271,14 @@ $
271271
272272## Questions and/or exercises
273273
274−And we're done with our very first Urbyte! Here's a question to
274+And we're done with our very first Urbyte! Here are some questions to
275275think about. These exercises are never mandatory, but they may
276276be fun and/or interesting. Skip them if they're obvious.
277277
278−The question today is: what is the right way to represent common
279−data structures as nouns? A linked list? A string? A *signed*
280−integer? A table or associative array? Just try to picture
281−these structures in your head, or draw them on a piece of paper.
278+* What is the right way to represent common
279+data structures as nouns?
280+* A linked list?
281+* A string? A *signed* integer?
282+* A table or associative array?
283+
284+Just try to picture these structures in your head, or draw them on a piece of paper.
docs/byte/1.md+5−5
@@ -349,21 +349,21 @@ As always, these questions are optional and only for fun.
349349We didn't include anywhere near all Hoon's auras or syntaxes in
350350this lesson. It's just a set of examples.
351351
352−Try using the dojo's magic error erasure to stumble around the
352+* Try using the dojo's magic error erasure to stumble around the
353353rest of Hoon's atom syntax. Any string that can't be extended
354354into a valid expression will be trimmed back, with a beep, until
355355it can. Return will beep if the expression is not complete.
356356This feedback is harmless and does not use an electric shock.
357357It enables stochastic reinforcement learning of Hoon syntax.
358358
359−If `~h6` is six hours, how do you write forty-five minutes? Two
359+* If `~h6` is six hours, how do you write forty-five minutes? Two
360360days, six hours and forty-five minutes?
361361
362−What would you expect the syntax for double-precision float to
362+* What would you expect the syntax for double-precision float to
363363be? What about base64?
364364
365−Does an absolute date have to include every zillisecond, or can
365+* Does an absolute date have to include every zillisecond, or can
366366it be pruned to a day or a year?
367367
368−If there's an IP syntax, what about bitcoin addresses? What
368+* If there's an IP syntax, what about bitcoin addresses? What
369369other auras do you think should be supported?