| winfredraj | Hello can you have a look at help me figure out the blunders I have made in this script -> it is dog slow right now which I really did not expect | 06:43 | |
| <script src="gist.github.com/winfredraj/8ddd71a...script> | |||
| I know Im doing zero optimisations etc, but when I ran the script for one error no it was acceptable and when I just extended it to around 10, it just stuck up on me | 06:46 | ||
| in WSL | |||
| so just want to know of its some memory setting or it was a blunder in the algorithm | 06:47 | ||
|
08:15
dakkar joined
|
|||
| antononcube | This link does shows “Not found” when pressed, and after I edit the link there is a blob on unstructured text. | 13:16 | |
| rcmlz | @simona6822 Raku is considered an „important language“ in some schools (on Planet Earth already)? That is interesting. I thought of Raku as underrated secret weapon you can do/learn/show all kinds of programming concepts. Regarding your question: I do not understand it. Are you looking for the „most important feature added in a specific year“? | 14:03 | |
| antononcube | @simona The most important feature was added in 2023 -- those are my LLM packages/modules and "Jupyter::Chatbook". | 14:06 | |
| rcmlz | @simona6822 Anton is very modest - but I also like his packages (using Chatbook and Markdown::Grammar virtually daily) | 14:08 | |
| 😀😀😀 | 14:13 | ||
| antononcube | @simona & @rcmlz More seriously: - The most important features of Raku were in it "from the get go" -- Grammars and CLI script facilitation - The combination / duo LLM<->Raku is great because Raku is made to process text | 14:18 | |
| rcmlz | Regarding the CLI I have a question. When validating the parameters of MAIN directly in the signature - on missmatch, how can I make Raku indicate which parameter was wrong? | 16:08 | |
| antononcube | @rcmlz I assume using “Getopt” would work. | 16:19 | |
| Alternatively/ or, using &ARGS-TO-CAPTURE and $*USAGE. | 16:21 | ||
| rcmlz | I put an example here: gist.github.com/rcmlz/ffc91f482032...bc3ee0974e | 16:22 | |
| antononcube | Actually, this seems simpler : docs.raku.org/language/create-cli#...RATE-USAGE | ||
| rcmlz | So there is no build-in way that tells me (in my example): "Hey, parameter 'folder' is wrong" | 16:24 | |
| I am just wondering: Raku probably "knows", which parameter was wrong (otherwise it would not return the standard usage message), but this information is not presented to the user? Would that be something to improve on? Maybe just a little "-->" in front of the failing parameter would be enough? | 16:28 | ||
|
16:34
dakkar left
|
|||
| ab5tract | rcmlz: GENERATE-USAGE is the way to go | 20:17 | |
| tonyo | rcmlz: raku can't tell you which parameter is wrong in multi dispatch with reliability, particularly in complex cases. it can tell you that the args don't match any of the multi dispatch candidates with certainty. fez does something with trying to figure out what you might've meant to call and displays the info that way but the invocation pattern in fez is very clear: `fez <cmd> <...args>` | 20:49 | |
| eg, you have two MAIN signatures of: `'help', Int:D $abc` and `'help', Int:D $xyz`, the dispatcher and you invoke as `<script> help --abc --xyz`. which message should it show? | 20:51 | ||
| s/the dispatcher // | 20:52 | ||
| ab5tract | tonyo: can't that be resolved with GENERATE-USAGE? | 23:27 | |
| I mean, it takes some work but I think everything you would need is available | 23:29 | ||