« first day (1 day earlier)      last day (720 days later) » 

09:06
(=€_€)=
 
1 hour later…
10:21
> This PR adds quicks. I need a little help though lol.
What with?
I might be able to brainstorm some ideas
And then maybe implement them too if I figure out how
10:47
oh cool
let me implement some first
i hate opening more than 3 tabs at once
> This train with same arity if accumulator truthy
@lyxal how do i do ^^^
So for a start that obviously won't be done at parse time
That's going to have to be dynamically executed
One thing you could do is keep track of the last arity in a variable and when calling the train, give it that tracked arity if the accumulator is truthy
Actually maybe it could be somewhat done at parse time
The quick would make the arity of the train its acting on be a lambda
uh lets move on lol
Something like lambda x: last_arity if accumulator else x
i would implement that as something called runtime quicks
No no I think passing a lambda as the arity could work for parse time
Then when evaluating the train, you just check if the arity type is types.FunctionType
And if it is, call the lambda
10:56
ok that makes sense
    '¨': attrdict(condition=lambda links: links and links[0].arity == 1,
        qlink=lambda links, outer_links, i: [attrdict(arity=links[0].arity, call=lambda x, y=None:[*map(links[0].call, x)])]),
@lyxal hows ^ for map
i hate pyright :/
@PyGamer0 seems awfully convoluted
Does it really need a condition?
Because maybe you could just make it so that it forces it to have arity 1
Dyads repeat their argument and nilads just fill the list
 
2 hours later…
12:46
@lyxal ooh thats a nice idea
@lyxal what does convoluted mean?
12:58
Unnecessarily complicated
Overbloated/a bit too complicated

« first day (1 day earlier)      last day (720 days later) »