- prepend each entry with aisle number

- sort by number

- remove aisle number

or, of course, you can outsource your brain, it might turn out to be less resource-expensive

https://www.fortinet.com/resources/cyberglossary/data-securi...

https://en.wikipedia.org/wiki/Data_security

https://www.nccoe.nist.gov/data-security

etc

all of these start with “unauthorized access” to define this term. can you please explain how open access to private repositories is not unauthorized access and how you can’t expect your data moving to private repositories to be private?

and ternary is a branch with no variable introduction, so it doesn’t apply again.

(it’s basically a weak switch expression, and the value moves leftwards towards its invocation.)

in general, I like zig syntax, but i find that it had very little regard to how the eye moves on the page. it’s jarring at times.

plus, there are still big-endian protocols that will stay for a long time. for example, MIDI clip files in MIDI 2.0 are big-endian.

zig is on its way to improving compilation times in its own pace and does so for the benefit of the project and everyone involved, so what is left to care for about bun by anthropic’s past?

the upcoming releases are expected to provide a solution to this “dispatch is comptime-known, but still dynamic” problem, and drop the loses in efficiency.