Expand `stdlib` with HOF

[jorgenosberg]

Maybe brunost could get a few standard HOF with some fun Nynorsk keywords? E.g.:

• .filter -> .sil
• .reduce -> .kok
• .take/.slice -> .skive
• .flatten -> .kjevle
• .map -> .støype

Not sure about names here, but just a few ideas that came to mind

[LFalch]

A lot of those are nouns. We should decide whether to makes them nouns or verbs and also what form to put them in. In English they are conveniently always both infinitive and imperative simultaneously. All of those words can be verbs and nouns in Norwegian too but we need to decide which.

I'm not familiar with a language where take and slice mean the same. take usually cuts off all but the N next items in an iterator/list/... whilst slice usually slices out a sub-array (a slice) or similar from a range. Those are similar but not the same functions, but I very much agree that skive is more fun.

[atomfinger]

I like the idea, but it should read like a reasonable nynorsk sentence.

For example, if we do minListe.sil... then that doesn't read well. Something like filtrere would read better even though it is less fun.

[LFalch]

miListe.sile reads just as well as miListe.filtrere

[jorgenosberg]

A lot of those are nouns. We should decide whether to makes them nouns or verbs and also what form to put them in. In English they are conveniently always both infinitive and imperative simultaneously. All of those words can be verbs and nouns in Norwegian too but we need to decide which.

I'm not familiar with a language where take and slice mean the same. take usually cuts off all but the N next items in an iterator/list/... whilst slice usually slices out a sub-array (a slice) or similar from a range. Those are similar but not the same functions, but I very much agree that skive is more fun.

Good point! However, all of these are valid imperative verb forms as is in Nynorsk. So we'd just need to decide on which form is preferable and stay consistent. E.g. "sil!" is valid, but also "sila!" and "sile!", just depends on consistency.

As for .take/.slice I meant that either could become .skive, but I'm not sure which. I guess .slice is the best candidate.

[atomfinger]

Hmm, possibly. Maybe I'm the problem for expecting something close to "filtering". Need to think it over and find something that feels right.

That said, I do want the whole HOF at some point.

[jorgenosberg]

I like the idea, but it should read like a reasonable nynorsk sentence.

For example, if we do minListe.sil... then that doesn't read well. Something like filtrere would read better even though it is less fun.

I may have gotten carried away with the "fun" aspect here. But the point still stands, we could probably turn most of these into useful HOF with reasonable nynorsk names, especially by allowing two words:

• .map() -> .gjerOm()
• .slice() -> .skjerUt()
• .reduce() -> .slåSaman()
• .flatten() -> .jamnUt()
• .take() -> .ta() or .tak()

They do work pretty well as more common verbs as well, so the fun aspect might not be all that important

[atomfinger]

If we ignore the exact working for a second, what do we feel about this syntax:

liste.gjerOm({ variabel -> 
        //... kode
    }
)

This is very Kotlin-coded, but it could get the job done, and that also includes support for anonymous functions (which I'm not against).

Any other suggestions?

[LFalch]

If we ignore the exact working for a second, what do we feel about this syntax:

liste.gjerOm({ variabel -> 
        //... kode
    }
)

This is very Kotlin-coded, but it could get the job done, and that also includes support for anonymous functions (which I'm not against).

Any other suggestions?

Could lean even more kotlin and just put the lambda block right after, letting final lambda arguments be passed in after (or instead of) parantheses like that:

liste.gjerOm { variabel ->
    // ... kode
}

[atomfinger]

Yeah, I like that one a lot.

[jorgenosberg]

I agree with the Kotlin direction here. Could also use det as the implicit Kotlin-style it.

liste.gjerOm { det * 2 }