On my bike this morning, I suddenly realised that ⊢⍤⌿⍥, (when the arguments have the same rank) can be written as ⍸⍛⊇
If argument ranks differ, then ⍸⍛⊇ is actually superior, as it works along leading axes, conceptually collapsing leading axes of the arguments until the left argument is a vector.
@Adám Ah! Took me a bit to see that. Very nice. It's a trifle sad that bottom horizontal bars all fail to line up pairwise with whatever font is getting used here.
Could be that they have consistently equated shifted state to non-shifted state where there's no assigned character for the shifted state. Check out U; does it give ↓?
Using f would make the best symmetry with ∘ on j (note that f and j are the "knobbed" keys), but it also makes sense to have ⍛ and _ together, and I dislike removing traditional bindings.
@Adám Ah, I hadn't seen the j-f symmetry. I tend to have biased preferences for beauty, symmetry and the like, but working in industry has corrupted me with another preference for not breaking the status quo.
Just out of curiosity, and if you can share, what does Dyalog's internal dev process look like? Vis-à-vis Hyrum's Law and Dyalog's age, I would imagine you need a large CI pipeline or something to ensure solid backwards compatibility.
@Adám Somewhat. Am interested in the details, actually, as much as can be shared at least.
The majority of my work is in devops and dev infrastructure development, so I'm really curious about the kinds of policies and tech in place on such a long-running project. I imagine it has gone through many evolutions.
@B.Wilson We don't really have secrets at Dyalog, other than user and customer information. However, I'm neither in operations, nor management, so my knowledge is limited.
@B.Wilson We use SVN and Git to track changes, Mantis and GitHub issues for tracking issues. Any changes to a primitives and a currently released version must go through full peer review. Internal knowledge sharing and project management is on an internal MediaWiki. New developments (other than bug fixes) have project plans with sign-offs from multiple parties: CTO, Architect, User Representative, Development Manager, Documentation Manager, QA Manager, and Software Security Group.