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

  • 1 Post
  • 72 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.









  • True, but it’s uniquely bad in the JS world. Developers tend to rely on libraries in almost cartoonish excess.

    • The language is shit in general, leading to an endless parade of frameworks and packages designed to paper over the sore spots.
    • The lack of a well-rounded One True Standard Library™ means lots of trivial functionality needs to come from somewhere.
    • Micro-dependencies are commonplace, leading to bloated dependency trees. I’d guess this is caused by a combination of both culture and the fact that you often want your JS artifacts to be as lean as possible.