Meta tags:
description=On the way with a camel and a butterfly.;

Headings (most frequently used words):

raku, playing, perl, b6xa, smuggling, pairs, my, for, autoarraying, missing, virtuousness, incomplete, ranges, spawnratelimiting, dodging, segfaults, parenthood, take, issue, with, enshittification, saying, them, apart,

Text of the page (most frequently used words):
the (87), and (37), that (36), raku (34), sub (29), with (26), use (23), can (21), foo (21), this (18), for (18), are (15), have (14), but (14), export (13), array (13), will (12), multi (12), name (11), say (11), categories (10), str (10), gfldex (10), thing (10), seepy (10), comment (9), all (9), there (9), because (9), one (9), time (9), child (9), quicksort (9), spawn (9), don (8), things (8), method (8), quite (8), need (8), 2023 (8), work (8), would (8), children (8), way (8), grep (8), you (7), now (7), should (7), routine (7), renamed (7), does (7), doing (7), before (7), not (7), has (7), new (7), indent (7), list (7), many (7), heavy (7), doesn (6), just (6), they (6), them (6), about (6), issues (6), how (6), limit (6), from (6), rakudo (6), having (6), root (6), node (6), any (6), into (6), junction (6), trans (6), start (5), free (5), create (5), playing (5), perl (5), b6xa (5), problem (5), issue (5), latter (5), more (5), proto (5), tmp (5), 2021 (5), line (5), few (5), well (5), hyper (5), like (5), get (5), map (5), class (5), could (5), arguments (5), pivot (5), dispatcher (5), range (5), dir (5), transporter (5), website (4), wordpress (4), com (4), make (4), nqp (4), call (4), break (4), output (4), block (4), while (4), hand (4), type (4), same (4), github (4), then (4), markdown (4), here (4), following (4), another (4), tree (4), base (4), child2 (4), some (4), obj (4), parent (4), signature (4), opts (4), named (4), after (4), function (4), code (4), what (4), question (4), lazy (4), path (4), rename (4), your (3), comments (3), back (3), got (3), might (3), without (3), see (3), know (3), aka (3), role (3), int (3), failer (3), answer (3), unit (3), source (3), take (3), their (3), out (3), little (3), api (3), move (3), reddit (3), less (3), wish (3), good (3), old (3), days (3), safe (3), become (3), base2 (3), walk (3), our (3), package (3), declarator (3), metamodelx (3), classhow (3), done (3), push (3), other (3), please (3), caller (3), enum (3), capture (3), gfm (3), hardbreaks (3), unsafe (3), full_info_string (3), numeric (3), turn (3), best (3), production (3), test (3), very (3), elements (3), rest (3), args (3), special (3), love (3), dwim (3), variance (3), light (3), been (3), value (3), around (3), 2024 (3), nums (3), self (3), own (2), log (2), sign (2), site (2), blog (2), come (2), rakuast (2), via (2), seems (2), backtrace (2), change (2), why (2), irc (2), was (2), core (2), callable (2), orig (2), renamedmulti (2), inter (2), stringer (2), failure (2), dispatch (2), return (2), however (2), candidates (2), allows (2), better (2), when (2), names (2), yes (2), text (2), july (2), uncategorized (2), eventually (2), services (2), money (2), actually (2), mix (2), solving (2), enshittification (2), case (2), want (2), needs (2), too (2), script (2), testing (2), hope (2), land (2), cmark (2), user (2), result (2), repo (2), often (2), being (2), right (2), great (2), let (2), wrong (2), where (2), dozens (2), running (2), trivial (2), object (2), types (2), lib (2), parents (2), found (2), exporthow (2), monkey (2), eval (2), declare (2), eoh (2), constant (2), seepyhow (2), metamodel (2), also (2), add_parent (2), add_child (2), teach (2), each (2), its (2), first (2), store (2), always (2), mine (2), objects (2), blogpost (2), true (2), nativecall (2), think (2), module (2), operator (2), bit (2), html (2), default (2), sourcepos (2), nobreaks (2), normalize (2), validate_utf8 (2), smart (2), github_pre_lang (2), liberal_html_tag (2), footnotes (2), strikethrough_double_tilde (2), table_prefer_style_attributes (2), cmark_options (2), keys (2), nice (2), sport (2), ask (2), driven (2), programmers (2), complete (2), fairly (2), easy (2), error (2), 65536 (2), collect (2), argument (2), promise (2), values (2), calls (2), thought (2), october (2), already (2), provide (2), scientists (2), which (2), ranges (2), over (2), infix (2), consider (2), made (2), operators (2), returned (2), clearly (2), elems (2), incomplete (2), year (2), magic (2), handling (2), head (2), may (2), produced (2), larry (2), compiler (2), hard (2), provided (2), wasn (2), happy (2), seq (2), files (2), makes (2), feed (2), whitespace (2), space (2), passing (2), early (2), statement (2), called (2), camel (2), butterfly (2), must, post, logged, loading, collapse, bar, report, content, manage, subscriptions, view, reader, privacy, account, subscribed, subscribe, top, older, entries, once, away, complaining, next, topic, pressing, indirectly, opcodes, subroutine, thanks, enquiry, fruitless, believe, pos, pm6, trickery, trait_mod, init, set_name, decont, fail, 2416, 2420, reading, spotted, lizmat, she, defines, readability, especially, debugging, different, cheat, doc, rakudoc, saying, apart, prepare, trackers, pay, investors, costing, again, happen, sooner, later, doubt, shrinking, workforces, zero, interest, rates, order, alternatives, cache, individual, locally, hour, far, within, day, external, dependencies, sadly, shell, none, modules, handle, reliably, slows, down, mostly, plenty, publish, earnest, coming, week, sufficient, proc, async, message, rate, exceeded, 426613, locations, trying, secure, rakudos, query, basically, consists, simple, url, suffice, turns, vendor, lock, button, fetch, scraper, increasing, load, companies, servers, figure, git, clone, amusement, watch, discussion, worries, changes, wishes, usenet, traded, robust, decentralised, platforms, require, clicks, reach, had, mirrors, interruptions, intertubes, common, miss, ability, access, documentation, machines, ddos, exactly, localhost, docs, org, inheritance, seep, through, plot, patch, full, dump, defined, registered, composable, fashion, explained, previously, hides, callsame, announce, arrival, classing, overloading, place, classes, introspectiveness, welcome, greg, donald, itch, refer, omitted, objective, reminded, written, bram, moolenaar, hero, memory, august, parenthood, generations, hopefully, generation, segmentation, faults, ofun, part, transparent, isn, simplify, hash, cmark_markdown_to_html, encode, utf, bytes, trick, heading, fighting, flavoured, stepped, onto, idiom, libs, enjoy, enums, hide, bitmasks, hence, interface, binary, operations, side, september, dodging, segfaults, least, destructuring, ready, awful, program, fancy, wait, hours, tests, large, datasets, much, these, project, slowly, grows, database, fails, runtime, bug, flat, roll, join, flattened, lists, limited, 65535, 2601, 2611, getting, trouble, oversharing, slip, await, either, whatever, returns, convert, atomicint, leave, wrapping, two, threads, ergo, takes, limits, blocks, keeps, insisting, ago, rcmlz, wished, parallelise, facility, recursion, oodles, cores, regard, double, tail, spawnratelimiting, easily, fixed, adding, multis, tools, those, bars, reason, language, looks, defaults, coercing, comparing, numerically, real, granted, yet, covers, former, everywhere, feels, uncompleted, tell, silly, unnecessary, agree, cased, cannot, 2629, lately, popped, numericaliness, enough, given, big, unhappiness, santa, race, moving, decision, callee, such, author, forms, boilerplate, able, generalisation, transforming, help, tings, degree, bouncing, until, collided, thoughts, raceseq, hyperseq, goes, illusion, deal, parallel, tricks, play, untangle, guarantee, allowed, short, circuit, according, laziness, virtue, somebody, else, kindly, fair, both, offload, burden, team, did, smokemachine, request, november, missing, virtuousness, merry, christmas, questions, obvious, telling, coersion, really, distinguish, anything, elegant, heavily, digesting, sofa, kept, rolling, wanted, wrap, rather, intrusive, likely, itself, thinking, ended, indexable, container, assignment, solution, immutability, hindering, indeed, zeekar, december, autoarraying, adds, tempting, requires, spaces, filenames, audio, video, auto, friendly, using, cli, bumpy, teaching, providing, rules, understood, job, wouldn, surprised, learn, anonymous, subs, emergent, behaviour, typing, augment, unless, apostrophe, prime, print, put, armed, simpler, abc, bbc, cbc, xic, iic, cic, title, states, bigger, lol, context, calling, supporting, wonder, added, syntax, goal, mind, becomes, possible, 5532, synopsis, february, kinds, stuff, long, everything, known, pretty, compile, truly, bird, idea, redispatch, advantage, excellent, refering, explicitly, needed, predefined, hidden, binding, rakumod, functional, raised, ever, helpful, left, didn, data, evaluates, expression, raiph, smuggling, pairs, archive, home,

Text of the page (random words):
atch the value that is produced by that function to take advantage of raku s excellent signature binding the proto and refering to sub export explicitly is needed because there is also a predefined and in this case hidden package called export i m passing on named arguments to export but all kinds of stuff could be returned by transporter so long as everything is known pretty early on at compile time the use statement is truly an early bird categories raku my raku for february 25 2024 gfldex 1 comment as the title states i made raku bigger because lol context that s how the synopsis is calling makes supporting feed operators fairly easy i wonder if larry added this syntax to signature with that goal in mind with pr 5532 the following becomes possible abc bbc cbc trans a x b i say output xic iic cic armed with this i can make a script of mine a little simpler use monkey typing augment class io path method trans c my from self str my to self str trans c self rename to unless from eq to sub rename whitespace io path dir where d dir dir grep d f rw trans c space c no break space c apostrophe c prime sub a print for a dir dir grep d rw routine rename whitespace io put i don t like spaces in filenames as they are often found with audio or video files having auto complete friendly names makes using a cli less bumpy by teaching io path to rename files by providing rules as they are understood by str trans i can use a feed operator to get the job done i wouldn t be surprised to learn that anonymous subs dwim here to be emergent behaviour in raku having another pr that adds trans to io path is tempting but requires more thought categories raku autoarraying december 25 2023 gfldex 1 comment over on reddit zeekar wasn t too happy about raku s love of seq it s immutability can be hindering indeed my nums 1 10 nums 0 grep 2 nums 0 push 11 we can t push to a seq i provided a solution i wasn t happy with it doesn t dwim and is anything but elegant so while heavily digesting on my sofa it is this time of the year the problem kept rolling around in my head at first i wanted to wrap array grep but that would be rather intrusive and likely break rakudo itself after quite a bit of thinking i ended up with the question how can i have indexable container aka array that will turn each value on assignment into an sub array my array foo 1 10 dd foo array array any foo array array any new 1 2 3 4 5 6 7 8 9 10 foo 0 grep 2 foo 1 42 dd foo array array any foo array array any new 1 3 5 7 9 42 the answer is obvious by telling the compiler what i want coersion types have become really hard to distinguish from magic i wish you all a merry christmas and the very best questions for 2024 categories raku missing virtuousness november 10 2023 gfldex 1 comment according to larry laziness is a programmers virtue the best way to be lazy is having somebody else do it by my request smokemachine kindly did so this is not fair we both should have been lazy and offload the burden to the core team please consider the following code my many things 1 10 list sub doing one thing at a time foo say doing one thing at a time many things all rakudo goes out of it s way to create the illusion that sub doing one thing at a time can deal with a junction it can t the dispatcher does all the work of running code in parallel there are tricks we can play to untangle a junction but there is no guarantee that all values are produced junction s are allowed to short circuit this was bouncing around in my head for quite some time until it collided with my thoughts about range we may be handling hyperseq and raceseq wrong my many things 1 10 list sub doing one thing at a time foo say doing one thing at a time many tings hyper degree 10 as with junction s doing dispatch magic to make hyper race just work moving the handling to the dispatcher would move the decision from the callee to the caller and as such from the author of a module to the user we can do that by hand already with hyper grep foo or other forms of boilerplate in raku land we should be able to do better and provide a generalisation of transforming calls with the help of the dispatcher i now know what to ask santa for this year categories raku incomplete ranges october 24 2023 gfldex 3 comments lately some unhappiness has popped up about range and it s incomplete numericaliness having just one blogpost about it is clearly not enough given how big range s can be say elems cannot elems a lazy list in block unit at tmp 2021 03 08 raku line 2629 i don t quite agree with rakudo here there are clearly elements in that lazy list this could very well be special cased the argument has been made that many operators in raku tell you what type the returned value will have is that so this question is always silly or unnecessary say 1 2 3 what junction granted junction is quite special but so are range s yet raku covers the former everywhere but the latter feels uncompleted please consider the following code multi sub infix numeric n numeric variance range n variance n variance say 2 6 2 0 5 true my heavy or light 25 6 50 3 75 4 88 8 heavy or light map _ 75 0 5 _ is light _ is heavy say 25 6 is heavy 50 3 is heavy 75 4 is heavy 88 8 is heavy to me that looks like it should dwim it doesn t because infix defaults to coercing to real and then comparing numerically this could easily be fixed by adding a few more multis and i don t think it would break any production code we already provide quite a few good tools for scientists and those scientists do love their error bars which are ranges i would love for them to have another reason to use raku over that other language categories uncategorized spawnratelimiting october 9 2023 gfldex 1 comment irc keeps insisting on being a good source of thought a few days ago rcmlz wished to parallelise quicksort raku doesn t sport a facility to make recursion just work with oodles of cores quicksort is a little special in that regard as it has a double tail call quicksort before pivot quicksort after just wrapping the two calls into start block will spawn way to many threads ergo i need a function that takes another function and it s arguments and limits the use of start blocks my atomicint spawn limit 8 sub spawn c args dd spawn limit spawn limit 0 spawn limit start leave spawn limit c args c args this routine will either return whatever c returns or a promise i need a way to convert the latter to values sub collect things slip things map thing thing promise await thing thing now i can change quicksort without getting into trouble with oversharing objects multi quicksort multi quicksort pivot rest my before rest grep before pivot my after rest grep before pivot flat collect spawn routine dispatcher before pivot spawn routine dispatcher after my a a z roll 12 join xx 2 16 say quicksort a output flattened array has 65536 elements but argument lists are limited to 65535 in sub quicksort at tmp 2021 03 08 raku line 2601 in block unit at tmp 2021 03 08 raku line 2611 well i could if rakudo would be production ready this bug is old and awful test driven programmers like to program test driven but don t fancy to wait for hours to see tests complete as a result very few test with large datasets and 65536 elements is not much these days it s fairly easy to start with a project in production that slowly grows it s database and eventually fails with a runtime error at least for now destructuring is best done by hand categories raku dodging segfaults september 10 2023 gfldex 2 comments while fighting with nativecall to get github flavoured markdown to work i stepped onto a nice idiom as many c libs cmark gfm does enjoy enums that hide bitmasks they have to do that because c doesn t sport named arguments raku does and hence a nice interface would not ask for binary operations on the caller side markdown gfm to html heading 1 unsafe hardbreaks full_info_string now i need a way to turn the named arguments into a list so i can use that as keys in of enum a capture in the signature of the sub will do the trick multi sub markdown gfm to html str d str opts default sourcepos hardbreaks safe unsafe nobreaks normalize validate_utf8 smart github_pre_lang liberal_html_tag footnotes strikethrough_double_tilde table_prefer_style_attributes full_info_string str d enum cmark_options default 0 sourcepos 1 1 hardbreaks 1 2 safe 1 3 unsafe 1 17 nobreaks 1 4 normalize 1 8 validate_utf8 1 9 smart 1 10 github_pre_lang 1 11 liberal_html_tag 1 12 footnotes 1 13 strikethrough_double_tilde 1 14 table_prefer_style_attributes 1 15 full_info_string 1 16 my opts cmark_options opts hash keys numeric cmark_markdown_to_html str str encode utf 8 bytes opts raku allows us to store part of a signature in a capture the latter will be transparent for the caller of the callable having to use a hyper method call operator isn t that great so the enum could become a map to simplify things a bit if you wish to use nativecall please do but think of the generations to come that will use your module hopefully they will like c less then our generation does segmentation faults are not ofun categories raku parenthood august 6 2023 gfldex 1 comment this blogpost is written in memory of bram moolenaar a true hero of text greg donald reminded me of an old itch of mine any object does refer to its base class but the other way is omitted so the objective is to teach type objects that are metamodelx classhow to know their children first i need a place to store the list of sub classes some introspectiveness is always welcome so a role is it role seepy has children method add_child mu obj mu child children push child method children mu obj children list now i need to teach each child class to announce its arrival to the parent this can be done by sub classing metamodel classhow and overloading method add_parent class metamodelx seepyhow is metamodel classhow also does seepy method add_parent mu obj mu parent hides parent add_child obj if parent how seepy callsame i can export my new class declarator in a composable fashion as explained previously our package exporthow sub export declarator name registered use monkey see no eval our exporthow declare eval q s to eoh package declare constant declarator name metamodelx seepyhow eoh map new let s do some testing source can be found here use v6 d use lib use seepy seepy seepy root seepy base is root seepy child is base seepy base2 is root seepy child2 is base2 my c1 child new dd c1 parents 0 children my c2 child2 new dd c2 parents 0 children sub walk tree mu u node c int indent mu u node indent 0 c indent node for node children child walk tree child c indent 1 walk tree root int indent mu u node say node name indent indent 2 output child child2 root base child base2 child2 by having inheritance seep through to a root object it has become trivial to plot a type tree now i can patch rakudo to do the same to get a full dump of all types defined in raku categories raku i take issue with enshittification july 2 2023 gfldex 1 comment with great amusement i watch the discussion of worries about let s call them changes of reddit on reddit the op wishes usenet to be back and yes we traded robust and decentralised services for platforms that require less clicks to reach them don t get me wrong i don t wish the good old days back when we had a need for mirrors because interruptions of the intertubes where quite common however i do miss the ability to access documentation without the need of dozens and dozens of machines to all work at the same time is docs raku org ddos safe i hope so because running that site on localhost is not exactly trivial i like to query the issues for rakudo and the problem solving repo quite often the latter basically consists of issues being on github a simple git clone with the right url should suffice right well as it turns out github is a vendor and issues are the lock in you can move issues from one repo to another but there is no export button there is an api to fetch them one by one if they would not have an api we would have to use a scraper increasing the load on that companies servers go figure while trying to secure rakudos issues i got the following result message api rate limit exceeded for user id 426613 locations that s about in i do cache individual issues locally so in an hour i should have them all in case you want to do the same here is how far i got within a day it needs more work and there are external dependencies sadly i have to shell out to cmark because none of the modules on raku land can handle markdown reliably that slows things down mostly because hyper and proc async don t mix too well the script needs a little more work and plenty of testing before i can publish it in earnest i hope the coming week will be sufficient enshittification is a thing and we should prepare for that there are alternatives to github and issue trackers eventually the free services we use will have to pay their investors with money actually costing money again that might happen sooner then later i doubt that shrinking workforces and zero interest rates mix there seems to be a problem solving issue in order categories uncategorized saying them apart july 2 2023 gfldex 1 comment while reading the source of rakudoc to text i spotted lizmat doing dispatch by hand she defines quite a few sub s that all take a rakuast doc type and return a str however they are multi candidates of the same proto this allows for better readability especially when debugging can we have multi candidates with different names yes but we need to cheat multi sub trait_mod is routine r renamed my orig r name init use nqp r set_name nqp decont renamed aka orig role renamedmulti name method name name r does renamedmulti renamed proto sub foo is renamed foo proto multi sub foo int is renamed inter say routine name multi sub foo str is renamed stringer say routine name multi sub foo failure is renamed failer fail oi foo 42 foo answer foo failure output inter stringer oi in sub failer aka failer at tmp 2021 03 08 raku line 2416 in block unit at tmp 2021 03 08 raku line 2420 as you can see i have to indirectly use a nqp opcodes to change the name of the subroutine thanks to nqp trickery in backtrace pm6 why method at pos doesn t just call name on the callable i don t know and my enquiry on irc was fruitless i believe it should but that might break things in core i will come back to this problem once we got v6 e rakuast might make the backtrace problem go away without me complaining via an issue the latter will be my next topic and seems to be a more pressing issue categories raku older entries top create a free website or blog at wordpress com playing perl 6 b6xa raku create a free website or blog at wordpress com subscribe subscribed playing perl 6 b6xa raku sign me up have a wordpress com account log in now privacy playing perl 6 b6xa raku view site in reader manage subscriptions sign up log in report this content collapse this bar lo...