🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm Set by lizmat on 8 June 2022. |
|||
00:00
reportable6 left
00:01
reportable6 joined
01:30
nine left,
nine joined
03:30
evalable6 left,
linkable6 left
03:31
linkable6 joined,
evalable6 joined
04:48
squashable6 left,
bisectable6 left,
statisfiable6 left,
notable6 left,
releasable6 left,
sourceable6 left,
evalable6 left,
bloatable6 left,
committable6 left,
quotable6 left,
reportable6 left,
nativecallable6 left,
shareable6 left,
benchable6 left,
tellable6 left,
unicodable6 left,
coverable6 left,
linkable6 left,
greppable6 left,
reportable6 joined,
unicodable6 joined
04:49
squashable6 joined,
quotable6 joined,
nativecallable6 joined,
tellable6 joined,
coverable6 joined,
benchable6 joined,
shareable6 joined,
evalable6 joined
04:50
bloatable6 joined,
sourceable6 joined,
statisfiable6 joined,
greppable6 joined,
bisectable6 joined,
releasable6 joined,
committable6 joined
04:51
linkable6 joined,
notable6 joined
05:12
Xliff joined
05:49
Xliff left
06:00
reportable6 left,
reportable6 joined
06:32
kurahaupo left
06:59
kjp left
07:00
uzl[m] left
07:02
kjp joined
07:09
japhb left
07:52
japhb joined
07:57
sena_kun joined,
japhb left
08:41
uzl[m] joined
08:43
japhb joined
08:47
japhb left
09:10
Xliff joined
10:31
evalable6 left,
linkable6 left
10:32
evalable6 joined
10:33
linkable6 joined
11:15
codesections joined
|
|||
lizmat | I've gathered my thoughts around supporting =table in RakuAST in gist.github.com/lizmat/02ac012fe1a...e31d9d151b | 11:30 | |
comments / suggestions etc welcome | 11:31 | ||
11:45
codesections left
|
|||
ugexe | will we be able to parse all the pod out of a rakumodule file on install and save it somewhere (preferably precompiled) once that stuff is done? | 11:55 | |
lizmat | yes | 11:56 | |
several options: serialize the RakuAST tree, with only the RakuAST::Doc objects in it | 11:57 | ||
s/serialize/precomp | 11:58 | ||
or serialize the RakuAST tree in any other format: markdown / man comes to mind | |||
nine | all of the above :) | 11:59 | |
lizmat | yup | ||
12:00
reportable6 left
12:01
reportable6 joined
|
|||
patrickb | are column headings possible? i.e. the first column is the header, not the first row. (what about first column and row as headers?) | 12:02 | |
lizmat | column headings are just the way you fill the first column, no? | 12:03 | |
score | 42 | 666 | |||
age | 18 | 66 | |||
patrickb | It's the divider that determines whether something is a header, right? | 12:04 | |
lizmat | if the first and second row divider do not use the same character, then the first row is a header | ||
that's my understanding of it | |||
patrickb | right. is the same possible with the first column? | ||
lizmat | I'm afraid I don't understand, could you gist an example ? | 12:05 | |
patrickb | will do | ||
12:08
squashable6 left,
squashable6 joined
|
|||
nine | In HTML this would be <table> <tr> <th>Primary:</th> <td>1</td> </tr> <tr> <th>Secondary:</th> <td>2</td> </tr> </table> | 12:11 | |
lizmat | ok, so you'd need a column to be marked to use <th> instead of <td> | 12:15 | |
I guess we could do this if the first column separator is different from the second | 12:16 | ||
patrickb | I just read up a tiny bit on Pod(docs.raku.org/language/tables.html). According to that page column headers are not a thing. | ||
lizmat | indeed, they are not at the moment | 12:17 | |
patrickb | THen I guess "Do we want to?" is a good question. "No" is an allowed answer. ;-) | ||
lizmat | well I think we do want to | 12:18 | |
patrickb | Do we want to be able to deparse a table char identical? | 12:19 | |
lizmat | I want it to be good enough to roundtrip | ||
looks like this: | |||
a | b + c | |||
========= | |||
x | 0 + y | |||
is currently valid table pod | 12:20 | ||
patrickb | Cells in the table are always identical width in a given column and identical height in a given row, right? | ||
lizmat | they don't need to be | ||
the number of dividers should be the same | 12:21 | ||
patrickb | oooh | ||
a | b | c | |||
lizmat | a | b + c | ||
========= | |||
x | 0 + y | |||
is the same as the above | |||
patrickb | ok | ||
but we can' mess with the row height at least? | 12:22 | ||
lizmat | yes, you can, if you use explicit row dividers | ||
patrickb | Wut? | ||
lizmat | yes, the magic world of pod6 tables :-) | 12:23 | |
docs.raku.org/language/tables.html..._practices see Heading and single- or multi-line content | |||
patrickb | OK. But not something evelish like: | 12:24 | |
a | b | c | |||
a ----- c | |||
--| d | c | |||
lizmat | a ----- c is not a valid row divider | 12:25 | |
so I guess that would be interpreted as a row with a single column | |||
patrickb | According to that page it is. | ||
lizmat | ? | 12:26 | |
patrickb | 5. For tables with no header and multi-line content, use one or more contiguous hyphens ('-') as the row separator in the content portion of the table. For example, | ||
lizmat | well, the wording may be confusing there: you cannot have anything else apart from contiguous - and whitespace around it | 12:28 | |
afk for a few mins | |||
patrickb | I get it. So the height of cells in a given row will always be identical. | ||
12:30
japhb joined
12:42
japhb left
|
|||
lizmat | yes | 12:53 | |
12:59
[Coke]_ joined
13:01
[Coke] left
13:02
[Coke]_ is now known as [Coke]
13:43
japhb joined
|
|||
Geth | rakudo/main: 4b69dd51e1 | (Elizabeth Mattijsen)++ | 2 files RakuAST: add some hooks for =table support development Add a few multi methods that will be called by default. This allows a script to augment these classes to put in the real version of the methods without needing to re-compile the whole core setting over and over again. |
15:15 | |
18:00
reportable6 left
18:01
reportable6 joined
|
|||
[Coke] | I have pressed the button to change master to main on MoarVM/MoarVM | 19:13 | |
[Tux]: ^^ | |||
jdv: ^^ | |||
19:51
linkable6 left,
evalable6 left
19:53
linkable6 joined
19:54
evalable6 joined
22:02
sena_kun left
23:02
bisectable6 left,
tellable6 left,
linkable6 left,
bloatable6 left,
unicodable6 left,
quotable6 left,
reportable6 left,
greppable6 left,
sourceable6 left,
squashable6 left,
releasable6 left,
notable6 left,
evalable6 left,
statisfiable6 left,
committable6 left,
nativecallable6 left,
coverable6 left,
shareable6 left,
benchable6 left
23:03
committable6 joined,
releasable6 joined,
bloatable6 joined,
statisfiable6 joined,
quotable6 joined,
squashable6 joined
23:04
unicodable6 joined,
sourceable6 joined,
bisectable6 joined,
evalable6 joined,
notable6 joined,
coverable6 joined,
nativecallable6 joined
23:05
reportable6 joined,
benchable6 joined,
linkable6 joined,
tellable6 joined,
greppable6 joined,
shareable6 joined
|