00:01 arkiuat joined 00:05 arkiuat left 00:13 arkiuat joined
Geth doc: arkiuat++ created pull request #4718:
addressed issue #4711 with minimal changes
00:40
01:05 librasteve_ left
Geth doc: arkiuat++ created pull request #4719:
Revise description of named arrays in create-cli.rakudoc
01:48
03:37 arkiuat left 03:45 disbot1 left, disbot2 joined 03:49 arkiuat joined 03:54 arkiuat left 03:55 arkiuat joined 06:51 arkiuat left 07:10 arkiuat joined 07:15 arkiuat left 07:28 arkiuat joined 07:32 arkiuat left 08:01 arkiuat joined 08:06 arkiuat left 08:19 arkiuat joined 08:30 arkiuat left 08:59 arkiuat joined 09:04 arkiuat left 09:26 arkiuat joined 09:31 arkiuat left 09:37 librasteve_ joined 09:59 arkiuat joined 10:05 arkiuat left 10:27 arkiuat joined 10:33 arkiuat left 11:03 arkiuat joined 11:08 arkiuat left 11:21 arkiuat joined 11:27 arkiuat left 11:46 arkiuat joined 11:51 arkiuat left 12:04 arkiuat joined 12:09 arkiuat left 12:29 arkiuat joined 12:34 arkiuat left 12:53 librasteve_ left 12:55 arkiuat joined 13:00 arkiuat left 13:17 arkiuat joined 13:22 arkiuat left 13:48 arkiuat joined 13:55 librasteve_ joined 13:57 arkiuat left 14:13 arkiuat joined 14:18 arkiuat left 14:22 arkiuat joined
arkiuat I think I'm going to take a break from docs issue #4560 for a bit and do something to address #3881. That's right up my alley and has been languishing for over four years 16:48
lizmat ++arkiuat 16:53
arkiuat the hardest part, for me, is going to be cutting the explanation down to the bare minimum required. I think that's what's appropriate here, and I can chatter on about leap seconds all day long, so what looks like the bare minimum to me is probably going to seem like a little too much to most folks 17:12
17:37 arkiuat left 17:49 arkiuat joined
[Coke] arkiuat++ 17:54
I responded to raiph's comment.
I find that he has VERY large comments that can hang people up, so trying to give a followup allowing us to proceed.
Geth doc/main: c5a4cb2545 | (Eric Forste)++ (committed using GitHub Web editor) | doc/Language/create-cli.rakudoc
Revise description of named arrays in create-cli.rakudoc (#4719)

It's not true that other subs can't use named arrays: they just work a little different than in sub MAIN
17:56
¦ doc: coke assigned to arkiuat Issue Make the role of "leap seconds" more obvious in DateTime and Instant github.com/Raku/doc/issues/3881
¦ doc: coke self-unassigned Make the role of "leap seconds" more obvious in DateTime and Instant github.com/Raku/doc/issues/3881
arkiuat [Coke]++ 18:04
I added a commit reversing the mistaken commit to Mu.rakudoc, so the PR should be okay now
and thanks for assigning that issue 18:05
18:28 finanalyst joined
arkiuat m: .say for (0..5).map({DateTime.new($start + $_ * $second)}).map({[.posix, $_]}) 18:42
camelia ===SORRY!=== Error while compiling <tmp>
Variable '$start' is not declared. Perhaps you forgot a 'sub' if this
was intended to be part of a signature?
at <tmp>:1
------> .say for (0..5).map({DateTime.new(<HERE>$start + $_ * $second)}).map({[.p…
arkiuat oops
m: my $i = Instant.from-posix(1483228798); my $s = DateTime.new(1) - DateTime.new(0); .say for (0..5).map({DateTime.new($i + $_ * $s)}).map({[.posix, $_]}) 18:46
camelia [1483228798 2016-12-31T23:59:58Z]
[1483228799 2016-12-31T23:59:59Z]
[1483228800 2016-12-31T23:59:60Z]
[1483228800 2017-01-01T00:00:00Z]
[1483228801 2017-01-01T00:00:01Z]
[1483228802 2017-01-01T00:00:02Z]
arkiuat there we go; that may well do as an example
I wonder if it would be possible to get a variance allowing actual linebreaks in the output instead of ␤ 19:10
that would make things a lot clearer. And I think I can get by with only four lines of output, not the six shown here 19:11
19:44 coleman left 19:45 coleman joined
arkiuat okay, now I'm looking at the phrase "UNIX timestamp"; I originally changed it to POSIX timestamp to be pedantically correct, except that everyone calls it Unix time. (There's a place for referring to it as POSIX time, and this isn't that place: we're in DateTime, not Instant). 20:29
Howevever, now the all-caps UNIX is really bugging me, so I'm changing it to "Unix timestamp" here. 20:30
so I'm making a couple of small additions to DateTime.rakudoc, but the big lump explaining leap seconds is going to be inserted into Instant.rakudoc before the current =head1 Future Leap Seconds. Here is a first draft of that gist.github.com/arkiuat/f4baa44430...414242e483 21:19
I think this is too long, but I have no idea which parts should get cut: suggestions solicited.
[Coke] the NL vs actual newlines has to be a separate discussion. :) 21:26
arkiuat yes, okay, I'm fine with that
right now, I'm just asking about verbiage
[Coke] I think whatever we decide on, we want consistency. I think we might want to go so far as having separate code blocks for output that are colored differently
reviewing draft... 21:27
It reads fine; I am only reading for style not accuracy. :) 21:28
arkiuat That's good, because I'm confident about the accuracy but full of misgivings about the style 21:29
[Coke] a few nits: "and which by that time" you can remove that which (it's repetitive) 21:30
arkiuat good point. removed. 21:32
[Coke] Instant should be a L<C<> nesting
arkiuat I cut more than just from that spot, I think it works better 21:33
well, yes to the C<> but I'm planning to put this text on the page that the L<> would link to, so... 21:34
[Coke] oh, then just C<>
the test is smart enough for that.
Sorry, didn't realize. 21:35
cool
arkiuat I put a link to the gist in a comment on issue #3881, soliciting further suggestions for cuts. Now I'm to step away from the keyboard for a bit. Thanks for your suggestions! 21:41
22:06 arkiuat left 22:09 arkiuat joined
arkiuat m: for 30, 31 { say DateTime.new(2016,12,$_,12,0,0).day-fraction } 22:58
camelia 0.5
0.499994
arkiuat that probably warrants adding a remark to DateTime.day-fraction also 22:59
23:54 finanalyst left