|
01:27
librasteve_ left
02:08
arkiuat left
|
|||
| coleman | coke I am late to this but you can delete my branch on Raku/doc if you need to | 03:31 | |
|
06:34
wayland joined
06:45
wayland left
|
|||
| Geth | doc/schultzdavid-patch-7: eb1715e364 | schultzdavid++ (committed using GitHub Web editor) | doc/Language/typesystem.rakudoc Add .WHERE to list of reserved methods This change was introduced with commit a0a198d and applies from Rakudo 2026.01. |
13:34 | |
| doc: schultzdavid++ created pull request #4767: Add .WHERE to list of reserved methods |
13:36 | ||
| doc/schultzdavid-patch-7: 9876867cbe | schultzdavid++ (committed using GitHub Web editor) | doc/Language/typesystem.rakudoc add indexing term for reserved method WHERE |
13:38 | ||
| doc/schultzdavid-patch-7: 9fef8927c8 | schultzdavid++ (committed using GitHub Web editor) | doc/Language/typesystem.rakudoc add DEFINITE and REPR to list of reserved methods as introduced by commits 6292774 and 971b2fa4 |
14:33 | ||
| doc/main: 7fa2210105 | (Will Coleda)++ | t/22-links-not-links.rakutest Revert "Add test to avoid non linked URLs." This reverts commit bb4981c8af29f961412a7f7194382554d0bff357. This branch was so old, the test was already part of another file |
15:47 | ||
| lizmat | i just spotted the text at docs.raku.org/syntax/BUILD | 16:27 | |
| I think the text of that should be completely rewritten to something that mentions that it is run *before* any attribute initialization, as opposed to TWEAK that runs *after* attribute initializations | 16:29 | ||
| lizmat is writing a blog post about BUILD / TWEAK at the moment, so maybe that can also serve as inspiration for a rewrite | 16:30 | ||
|
16:34
arkiuat joined
|
|||
| arkiuat | what is the difference between =item1 and =item tags in rakudoc? are they essentially synonymous? I understand that =item2, =item3 etc add levels of indentation for sublists (as in an outline-type structure) | 16:35 | |
| lizmat++ I've been wanting a better explanation of BUILD and TWEAK for a while | 16:37 | ||
| lizmat | arkiuat: working on it... maybe finished later today, otherwise tomorrow | ||
| arkiuat | It seems as the doc when I first started reading it all had been written when only BUILD existed, and then was very sparsely edited after TWEAK was added. I got the impression for my purposes that TWEAK would be more suitable than BUILD for my purposes 95% of the time, but at the time it was difficult to figure that out from the docs | 16:38 | |
| s/as/as if/ | |||
| lizmat | yeah, TWEAK should be the first choice, and BUILD only if really necessary | ||
| arkiuat | that's what I eventually concluded. But as of maybe a year ago the docs didn't really make that clear, and I don't think that part has been updated much since then | 16:39 | |
| lizmat | you would only need BUILD if it needs to provide a default for other attributes | ||
| arkiuat | thank you for taking this on | ||
| lizmat | well, all of these blog posts dev.to/lizmat/series/35190 are the result of the first resolutions meeting, really | 16:40 | |
| and now getting to TWEAK / BUILD :-) | |||
| arkiuat | right, I remember. I've really been enjoying this series of blog posts | ||
| lizmat | thank you :-) | ||
| arkiuat | oh right, they're both all-caps! | 16:41 | |
| so i'm guessing that =item and =item1 mean essentially the same thing, but that =item1 is more idiomatic when used in combination with =item2 etc and =item is more idiomatic in a flat one-level list. But I have no idea where to look this up: there are a lot of old rakudoc docs lying around and I don't know what's authoritative | 16:43 | ||
| lizmat | in rakudoc =item and =item1 at the renderer level are *not* the same | 16:44 | |
| =item basically has level "", and =item1 has level "1" | |||
| but I think all renderers so far do not make a difference between these two cases | 16:45 | ||
| when they render, I mean :-) | 16:46 | ||
| arkiuat | got it, thanks | 16:51 | |
| it is indeed from trying it out in some renderer or other that gave me that impression, but your explanation makes sense | |||
| [Coke] | lizmat++ blogging. | 17:09 | |
| Geth | doc/coke/x-cleanup: 15942ded1a | (Will Coleda)++ | t/18-rakuast-validate.rakutest wip |
17:13 | |
| doc/coke/x-cleanup: 779fc77835 | (Will Coleda)++ | t/18-rakuast-validate.rakutest Add test for ;'s in X<> meta attribute Part of #4099 |
|||
| doc/coke/x-cleanup: 4fa3c05423 | (Will Coleda)++ | t/18-rakuast-validate.rakutest Add test for ;'s in X<> meta attribute Part of #4099 |
|||
| [Coke] | (oops. collapsed that wip commit) | ||
| correct me if I'm wrong, but the easiest "fix" to those failures is to take X<|a,b;c,d> and replace it with X<|a,b>X<|c,d> | 17:16 | ||
| Geth | doc: arkiuat++ created pull request #4768: more detail for variable declarators and scope |
17:18 | |
| [Coke] | arkiuat: some test failures, FYI | 17:22 | |
| arkiuat | [Coke] right, I probably need a =begin code, maybe with a :skip-test | 17:23 | |
| there's a warning about unimplemented ... | |||
| but this is still draft | 17:24 | ||
| also an instance of "run-time" and one trailing whitespace, fixing those now | 17:37 | ||
|
17:48
Nemokosch joined
18:08
arkiuat left
|
|||
| [Coke] | arkiuat: try `# ...` instead of a raw `...` | 18:31 | |
|
18:32
arkiuat joined
|
|||
| arkiuat | [Coke], thanks. Done. | 18:35 | |
| [Coke] | it really didn't like the stub in the interior class definition. | ||
| er, more specifically on my previous one, X<a|b,c;d,e> should be X<a|b,c>X<a|d,e> ? | 18:38 | ||
| arkiuat | I should be paying attention because I self-assigned a couple of "add this thing to the index" issues so I could learn how to do it | 18:46 | |
| [Coke] throws a comment to finanlyst in the ticket. | |||
| Geth | ¦ doc-website: coke self-assigned Non-Raku code examples take up a lot of vertical space github.com/Raku/doc-website/issues/475 | 18:49 | |
| ¦ doc-website: coke assigned to finanalyst Issue Non-Raku code examples take up a lot of vertical space github.com/Raku/doc-website/issues/475 | |||
| ¦ doc-website: coke unassigned from finanalyst Issue Non-Raku code examples take up a lot of vertical space github.com/Raku/doc-website/issues/475 | |||
| ¦ doc-website: coke self-unassigned Non-Raku code examples take up a lot of vertical space github.com/Raku/doc-website/issues/475 | |||
|
18:53
ds7832 joined
|
|||
| [Coke] | github.com/raku/doc-website/issues/139 - any thoughts on using a CDN for js/css? I think the answer has moved from "hell yes" to "hell no" in the last decade. | 18:57 | |
| lizmat | as long as the js / css has a valid expiration / modified header, it should be ok after the initial load? | 19:04 | |
| etag: "dfx8cv2hbyf41t2-gzip" | 19:09 | ||
| last-modified: Sun, 25 Jan 2026 00:06:22 GMT | |||
| looks ok to me | |||
| coleman | add a hash and a CDN is fine (what liz said). browsers will check it | 19:28 | |
|
19:33
ds7832 left
19:34
ds7832 joined
19:44
Nemokosch left
19:47
ds7832 left
|
|||
| [Coke] | "is fine". is it preferred? | 19:48 | |
| the ticket is asking us to move to CDN. if either way is fine, not worth it. | |||
| We can do the same header setup for JSS/CSS served from our site. | 19:49 | ||
| nemokosch | is the X markup that creates the index entries? | 19:50 | |
| [Coke] | (index) yeS: docs.raku.org/language/pod#Indexing_terms | 19:57 | |
| ... not that you can read that section due to the rendering bug. :( | 19:59 | ||