git.iko.soy/urbit.org
on master help sign in
Merge pull request #178 from cxk280/dev
b9b7f3bFang
docs/arvo/network.md+1−1
compare with master
unifiedsplit
@@ -65,7 +65,7 @@ didn't exist. This is a slightly hacky way of printing to the console,
65but we'll get to the correct way later on.
65but we'll get to the correct way later on.
66
66
67But what does `++poke-noun` produce? Recall that `^-` casts to a type.
67But 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
69type `{(list) _+>.$}`. But what does this mean?
69type `{(list) _+>.$}`. But what does this mean?
70
70
71The phrase to remember is "a list of moves and our state". Urbit is a
71The phrase to remember is "a list of moves and our state". Urbit is a
docs/byte/0.md+8−5
@@ -271,11 +271,14 @@ $
271
271
272## Questions and/or exercises
272## Questions and/or exercises
273
273
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
275think about. These exercises are never mandatory, but they may
275think about. These exercises are never mandatory, but they may
276be fun and/or interesting. Skip them if they're obvious.
276be fun and/or interesting. Skip them if they're obvious.
277
277
278−The question today is: what is the right way to represent common
278+* What is the right way to represent common
279−data structures as nouns? A linked list? A string? A *signed*
279+data structures as nouns?
280+* A linked list?
281+* A string? A *signed* integer?
280−integer? A table or associative array? Just try to picture
282+* A table or associative array?
283+
281−these structures in your head, or draw them on a piece of paper.
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.
349We didn't include anywhere near all Hoon's auras or syntaxes in
349We didn't include anywhere near all Hoon's auras or syntaxes in
350this lesson. It's just a set of examples.
350this lesson. It's just a set of examples.
351
351
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
353rest of Hoon's atom syntax. Any string that can't be extended
353rest of Hoon's atom syntax. Any string that can't be extended
354into a valid expression will be trimmed back, with a beep, until
354into a valid expression will be trimmed back, with a beep, until
355it can. Return will beep if the expression is not complete.
355it can. Return will beep if the expression is not complete.
356This feedback is harmless and does not use an electric shock.
356This feedback is harmless and does not use an electric shock.
357It enables stochastic reinforcement learning of Hoon syntax.
357It enables stochastic reinforcement learning of Hoon syntax.
358
358
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
360days, six hours and forty-five minutes?
360days, six hours and forty-five minutes?
361
361
362−What would you expect the syntax for double-precision float to
362+* What would you expect the syntax for double-precision float to
363be? What about base64?
363be? What about base64?
364
364
365−Does an absolute date have to include every zillisecond, or can
365+* Does an absolute date have to include every zillisecond, or can
366it be pruned to a day or a year?
366it be pruned to a day or a year?
367
367
368−If there's an IP syntax, what about bitcoin addresses? What
368+* If there's an IP syntax, what about bitcoin addresses? What
369other auras do you think should be supported?
369other auras do you think should be supported?