« first day (570 days earlier)      last day (2085 days later) » 

1:15 AM
stupid bot was starred D:
 
 
8 hours later…
ngn
8:55 AM
@J.Sallé @dzaima another approach is to encode in base 100 and then encode each in base 10 10
the shortest i can get that way is 29 bytes, left as an exercise to the reader :)
 
9:23 AM
I have 34 :|
 
ngn
9:41 AM
@dzaima 27
 
ngn
9:52 AM
i haven't given out apl bounties lately, this looks like a good opportunity
I'll reward the shortest Dyalog APL answer to the digit pairs challenge published within 3 days from now with +50 rep for every byte below 35 (max +500 rep).
@Adám please pin ^
34 bytes ->  +50 rep
33 bytes -> +100 rep
32 bytes -> +150 rep
31 bytes -> +200 rep
30 bytes -> +250 rep
29 bytes -> +300 rep
28 bytes -> +350 rep
27 bytes -> +400 rep (known to be possible)
26 bytes -> +450 rep
25 bytes -> +500 rep
 
 
1 hour later…
ngn
11:28 AM
that was quick :) 26 is also possible
 
 
6 hours later…
5:20 PM
is there a reason that an A f train doesn't exist? e.g. (2+) 3 → 5
 
ngn
5:52 PM
@dzaima 2+⊢ is equivalent to {2}+⊢, so would 2+ be equivalent to {2}+?
 
@ngn hm, I always thought of arrays in trains as immediately assigning themselves as the left argument of the function to the right, not as fns returning themselves
 
ngn
@dzaima well, arrays in trains do affect the odd-even pattern, for instance -*1+⊢ works like -*({1}+⊢), not -(*(1∘+)⊢)
what do you think A f g h should do in your model?
 
@ngn ((A f ⍵) g (A h ⍵)), dyadically erroring (or ignoring )
 
ngn
6:09 PM
@dzaima interesting... what about A f B g? I suppose that's A f (B g ⍵)?
 
@ngn that doesn't currently work (as the 2-train is only checked at the end), but yeah, seems reasonable enough to be useful
and now (1+2×)5 returns 11
 
6:28 PM
@ngn really the even-odd pattern doesn't apply in my model anymore, but yeah, instead of immediately, I should've said after grouping the trains
 
ngn
@dzaima so, it's similar to how it works in k - there's no even-odd pattern there
(train)x is simply train x, no tricky rules
 
@ngn I should've probably learned at least a bit of K and J before making an APL derivative :p
@ngn does that mean that the classic +/÷≢ equivalent sums the reciprocal of the length?
 
ngn
@dzaima I think it's a useful experience to implement any of them. Each of the three has its own unique flavour.
@dzaima yes, except that the symbols are a little different
and no primitive is wasted for reciprocal: x%y is divide but %x is sqrt
 
@ngn My APL still has forks - (+/÷≢)1 5 6 still returns 4 just that I can do cool stuff like (1++/÷≢)1 5 6 for 5
 
ngn
@dzaima well, if I understood correctly, that particular fork is compatible with Dyalog and ngn/apl, but +/÷≢1+⊢ probably isn't
 
6:41 PM
@ngn why does that not work in ngn/apl?
oh, you just don't support have broken A f g forks
 
ngn
@dzaima huh... I've broken something there
 
ngn
6:58 PM
ok, now it works (but it takes some time for gitlab to flush its caches)
every time I look at my own code after a long pause, it looks horribly verbose :)
 
@ngn what should be incompatible there?
 
ngn
@dzaima didn't you say arrays in trains are bound to the function immediately to the right?
I imagine it's like +/÷≢(1∘+)⊢
 
@ngn I corrected myself later
 
ngn
ah, sorry
 
7:51 PM
@ngn argh i want the reciprocal built-in but sqrt fits so nicely on ÷
 
ngn
@dzaima you have plenty of unicode chars :)
 
oh wait i was about to say that making only for monadic would feel pointless but then realized that there are roots other than square roots
 
 
3 hours later…
10:57 PM
@dzaima Yeah, I've long been wondering why APL hasn't had (square)root built-in. Well, now in Dyalog has *∘.5/*∘÷⍨ but those are pretty awkward for such a fundamental function. NARS has .
 

« first day (570 days earlier)      last day (2085 days later) »