Your friendly local programmer, uni student and *nix addict.

  • 1 Post
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle





  • Well, that’s to be expected - the implementation of map expects a function that takes ownership of its inputs, so you get a type mismatch.

    If you really want to golf things, you can tack your own map_ref (and friends) onto the Iterator trait. It’s not very useful - the output can’t reference the input - but it’s possible!

    I imagine you could possibly extend this to a combinator that returns a tuple of (Input, ref_map'd output) to get around that limitation, although I can’t think of any cases where that would actually be useful.



  • I don’t know about dangerous, but case-insensitive Unicode comparison is annoying, expensive and probably prone to footguns compared to a simple byte-for-byte equality check.

    Obviously, it can be done, but I guess Linux devs don’t consider it worthwhile.

    (And yes, all modern filesystems support Unicode. Linux stores them as arbitrary bytes, Apple’s HFS uses… some special bullshit, and Windows uses UTF-16.)